CVE-2026-77459: Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
argoproj · argo-cd
No fix listed · Affected: argoproj argo-cd · Exploitation: not established
At a glance
Higher than 43% of scored CVEs
What it isNVD
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 2.10.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, Argo CD creates PostDelete resource hooks without applying the AppProject destination and resource authorization checks used during ordinary synchronization.
The omitted checks include cluster-scoped and namespaced resource allow/deny lists.
A user who can write to an Application's Git repository can commit a delete hook targeting a forbidden namespace, server, group, kind, or resource name, and deletion of the Application causes the application-controller to create that resource with its destination-cluster credentials.
The reachable impact is bounded by the controller's cluster access but can include cluster-scoped resources, disallowed namespaces, persistent hook objects, and secondary objects created by a hook Job. PreSync, Sync, PostSync, and SyncFail hooks continue to use the normal project checks.
This issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.20 (20 Nov)
- Not establishedNothing in the sources we check
Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.
Weakness and public checks
- Public check
- No public nuclei template
- Weakness
- Incorrect Authorization · Access Control
Other CVEs in argo-cd
Every published CVE for argoproj argo-cd, by how far exploitation has gone. This one is among them.
Coverage1 article · 1 outlet
First in our coverage: SecurityOnline, 7 Oct.
- Argo CD Patches Four Critical Flaws That Could Expose Secrets and ClustersSecurityOnline · first in our coverage
New articles also arrive in the RSS feed.