Live › vulnerability › CVE-2026-77459
Go to dashboardArgo CD skips AppProject destination and resource allow/deny checks when it creates PreDelete/PostDelete hook resources, so anyone who can commit to an Application's Git repo can get the application-controller to create forbidden resources in other namespaces or cluster-scoped objects using the controller's cluster credentials. The attacker gets resource creation bounded only by the controller's cluster access, including persistent hook objects and Jobs.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/argoproj/argo-cd | go | all versions | – |
| github.com/argoproj/argo-cd/v2 | go | >= 2.10.0 | – |
| github.com/argoproj/argo-cd/v3 | go | >= 3.6.0-rc1, < 3.6.0-rc2 | 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2 |
2.10.0 and below the fixes, or v3 in 3.3.x below 3.3.15, 3.4.x below 3.4.10, 3.5.x below , or 3.5.43.6.0-rc1Upgrade Argo CD to 3.3.15, 3.4.10, 3.5.4, or 3.6.0-rc2 (or later in your release line).
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-77459")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.