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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-863"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/77xxx/CVE-2026-77459.json"
}{
"extracted_events": [
{
"introduced": "2.10.0"
},
{
"last_affected": "2.14.21"
},
{
"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"
}
],
"source": "AFFECTED_FIELD"
}