Summary
Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
Workarounds
There is no configuration setting that applies the project check to delete hooks while those hooks stay in use.
- Do not grant untrusted users write access to Git repositories that back Applications in restrictive AppProjects.
- Limit who can delete Applications. Deletion is what runs PreDelete and PostDelete hooks.
- Tighten the application-controller's Kubernetes access so a hook cannot reach sensitive namespaces or APIs.
Credits
The Argo CD team would like to thank @RealFakeAccount, @AdamKorcz, @0xshylines, @thevilledev, @HenriWilliams, @cherez0ff, @ARSB1, and @zwindler for responsibly disclosing this issue according to our security reporting guidelines.
References
- PostDelete introducing commit: dcc17f70bf7db973fe480b8b613189b2c5ac4b4b (#16595), first released in v2.10.0
- PreDelete introducing commit: 3bf3d8a2124e772ac651f3fd42375c4e9b8008af (#22288), first released in v3.3.0
- AppProject specification
- Resource hooks
For more information
- Open an issue in the Argo CD issue tracker or discussions
- Join us on Slack in channel #argo-cd
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 someone deletes it. Deleting the Application creates the hook. What that can reach is bounded by the application-controller's access to the destination cluster. In a typical install that access is broad, so a tenant can create a cluster-scoped object such as a ClusterRoleBinding, or an object in a namespace the project does not allow. A hook with no deletion policy is removed after it succeeds. A deletion policy that does not remove the hook on success leaves the object in the cluster. A hook such as a Job can create further objects that Argo CD does not clean up.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
CVE-2026-77459 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
A patch for this vulnerability has been released in the following Argo CD versions:
- v3.6.0-rc2
- v3.5.4
- v3.4.10
- v3.3.15
The fix applies the same AppProject destination and resource checks used on sync before creating a PreDelete or PostDelete hook.
Argo CD 2.x and 3.0 through 3.2 are out of support and will not receive a patch. Upgrade to a patched 3.3 or newer release.
Frequently Asked Questions
- What is CVE-2026-77459? CVE-2026-77459 is a critical-severity incorrect authorization vulnerability in github.com/argoproj/argo-cd/v2 (go), affecting versions >= 2.10.0, <= 2.14.21. It is fixed in 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- How severe is CVE-2026-77459? CVE-2026-77459 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-77459?
github.com/argoproj/argo-cd/v2(go) (versions >= 2.10.0, <= 2.14.21)github.com/argoproj/argo-cd/v3(go) (versions >= 3.0.0, < 3.3.15)
- Is there a fix for CVE-2026-77459? Yes. CVE-2026-77459 is fixed in 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2. Upgrade to this version or later.
- Is CVE-2026-77459 exploitable, and should I be worried? Whether CVE-2026-77459 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-77459 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-77459?
- Upgrade
github.com/argoproj/argo-cd/v3to 3.3.15 or later - Upgrade
github.com/argoproj/argo-cd/v3to 3.4.10 or later - Upgrade
github.com/argoproj/argo-cd/v3to 3.5.4 or later - Upgrade
github.com/argoproj/argo-cd/v3to 3.6.0-rc2 or later
- Upgrade