Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

Argo CD may create unauthorized resources on app delete

published 10 days ago
Summary

Versions of Argo CD from 2.10.0 up to 3.3.15, 3.4.10, 3.5.4, and 3.6.0‑rc2 can create resources without checking the usual permission rules when a delete hook runs. If someone can edit the Git repo for an application, they could cause the system to delete or create items in restricted areas of your cluster. Upgrade to the fixed releases or apply the latest patches to stop this behavior.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Alpine:3.24 docker hardened images argocd-3.3-dev All versions
Docker Hardened Images:Alpine:3.24 docker hardened images argocd-3.3 All versions
Docker Hardened Images:Alpine:3.24 docker hardened images argocd-3.4-dev All versions
Docker Hardened Images:Alpine:3.24 docker hardened images argocd-3.4 All versions
Docker Hardened Images:Alpine:3.24 docker hardened images argocd-3.5-dev All versions
Docker Hardened Images:Alpine:3.24 docker hardened images argocd-3.5 All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argocd-image-updater-dev All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argocd-image-updater-fips-dev All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argocd-image-updater-fips All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argocd-image-updater All versions
Original advisory text
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…
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.
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit (estimated)
  • Gives an attacker full control (estimated)
Severity
9.9 Critical
Timeline
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta