Quick answers
- Is CVE-2026-77459 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77459 being exploited in the wild.
- How severe is CVE-2026-77459?
- Critical severity, with a CVSS score of 9.9, published 13 October 2026.
- Which products and versions are affected?
- Argoproj Argo CD v2.10.0 through v3.2.x (PreDelete), v2.10.0 through v3.5.3, v3.4.0 through v3.4.9, v3.3.0 through v3.3.14 (PostDelete and PreDelete); github.com/argoproj/argo-cd (Go) SEMVER:introduced=0; github.com/argoproj/argo-cd/v2 (Go) >= 2.10.0, <= 2.14.21, SEMVER:introduced=2.10.0, SEMVER:introduced=2.10.0,last_affected=2.14.21; github.com/argoproj/argo-cd/v3 (Go) >= 3.0.0, < 3.3.15, SEMVER:introduced=3.0.0,fixed=3.3.15, SEMVER:introduced=3.0.0,fixed=3.3.15,introduced=3.4.0,fixed=3.4.10,introduced=3.5.0,fixed=3.5.4,introduced=3.6.0-rc1,fixed=3.6.0-rc2.
- Is there a fix for CVE-2026-77459?
- Yes. github.com/argoproj/argo-cd/v3 (Go): upgrade to 3.3.15, 3.6.0-rc2 or later. Until then: Restrict write access to Git repositories backing Applications in restrictive AppProjects to trusted users only. Limit deletion permissions for Applications to authorized personnel. Tighten the application-controller's Kubernetes role-based access control (RBAC) to prevent it from reaching sensitive namespaces or sensitive APIs. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77459 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-77459?
- Check whether you run Argoproj Argo CD, github.com/argoproj/argo-cd (Go), github.com/argoproj/argo-cd/v2 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/argoproj/argo-cd/v3 (Go): upgrade to 3.3.15, 3.6.0-rc2 or later
go get github.com/argoproj/argo-cd/v3@v3.6.0-rc2
Restrict write access to Git repositories backing Applications in restrictive AppProjects to trusted users only. Limit deletion permissions for Applications to authorized personnel. Tighten the application-controller's Kubernetes role-based access control (RBAC) to prevent it from reaching sensitive namespaces or sensitive APIs.
Technical details
Argo CD skips AppProject destination-namespace and resource-restriction checks when processing PreDelete and PostDelete resource hooks, while the same checks are enforced for PreSync, Sync, PostSync, and SyncFail hooks. An attacker with Git repository write access can define a hook with a namespace, group, kind, or name that would normally be denied by the AppProject policy; the hook is created and executed with application-controller credentials only when the Application is deleted. The scope of damage is limited by the controller's Kubernetes RBAC permissions, but in typical installations this allows creation of cluster-scoped resources or objects outside allowed namespaces.
Affected products
- Argoproj Argo CD v2.10.0 through v3.2.x (PreDelete), v2.10.0 through v3.5.3, v3.4.0 through v3.4.9, v3.3.0 through v3.3.14 (PostDelete and PreDelete)
Identifiers
- CVE-2026-77459
- BIT-ARGO-CD-2026-77459
- GHSA-fmxq-cgp8-87wp
- GO-2026-6784
Timeline
- 2026-10-15: disclosed