Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77459 critical CVSS 9.9

Authorization Flaw in github.com/argoproj/argo-cd/v2 (CVE-2026-77459)

Summary

Vulnerability in github.com/argoproj/argo-cd/v2 (CVE-2026-77459). Successful exploitation can lead to full system takeover. Exploitable via ClusterRoleBinding. Mitigation: upgrade to 3.6.0-rc2 or later.

Original description

The description as published by the source.

Impact

Argo CD checks an Application's AppProject before it creates resources during a sync. That check covers destination namespaces and servers, cluster-scoped resource allow and deny lists, and namespaced resource allow and deny lists, including resource names. PreDelete and PostDelete hooks skip it. When the Application is deleted, Argo CD creates those hooks with the application-controller's credentials on the destination cluster.

All versions from v2.10.0 onward are affected, including every currently supported release. v2.9.22 and earlier are not. PostDelete hooks were introduced in dcc17f70bf (2023-12-18, #16595) and first released in v2.10.0. That creation path has never applied the project check. PreDelete hooks, added in 3bf3d8a212 (2025-12-05, #22288) and first released in v3.3.0, use the same path. v3.2.12 and earlier do not have PreDelete hooks. PreSync, Sync, PostSync, and SyncFail hooks still go through the project check.

A user who can push to the Git repository an Application syncs from can commit a hook whose namespace, group, kind, or name the AppProject would refuse on sync. The controller adds the delete finalizer when it sees the hook, and the Application stays Synced until som…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-77459 has been found in github.com/argoproj/argo-cd/v2.
Attackers can target a specific entry point like ClusterRoleBinding over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/argoproj/argo-cd/v2 to 3.6.0-rc2 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-cd/v2 CVE-2026-77459" on the vendor's site.

CVE-2026-77459 (github.com/argoproj/argo-cd/v2) — CWE-863 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ClusterRoleBinding
Patched: 3.6.0-rc2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Incorrect authorization (CWE-863) exists in github.com/argoproj/argo-cd/v2. Attackers reach the vulnerable code path via ClusterRoleBinding.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/argoproj/argo-cd/v2. Attack surface: ClusterRoleBinding.

🔥 Severity

Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.6.0-rc2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/argoproj/argo-cd/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/argoproj/argo-cd/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/argoproj/argo-cd/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/argoproj/argo-cd/v2 to 3.6.0-rc2

    ステージング環境で 3.6.0-rc2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/argoproj/argo-cd/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
go github.com/argoproj/argo-cd/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.0-rc2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details