Loading
Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: >= 2.10.0, <= 2.14.21
Vulnerable: >= 3.0.0, < 3.3.15
Patched in 3.3.15
Vulnerable: >= 3.4.0, < 3.4.10
Patched in 3.4.10
Vulnerable: >= 3.5.0, < 3.5.4
Patched in 3.5.4
Vulnerable: >= 3.6.0-rc1, < 3.6.0-rc2
Patched in 3.6.0-rc2
Details
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.
A patch for this vulnerability has been released in the following Argo CD versions:
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.
There is no configuration setting that applies the project check to delete hooks while those hooks stay in use.
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.
EPSS, exploit probability
Low0.72%
estimated chance of real-world exploitation in the next 30 days, higher than 52.9% of every CVE FIRST.org scores
Refreshed 10/15/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.