Incorrect Authorization Affecting argocd-3.3-compat package, versions <3.3.15-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-ARGOCD33COMPAT-21152634
- published17 Oct 2026
- disclosed13 Oct 2026
Introduced: 13 Oct 2026
NewCVE-2026-77459 (opens in a new tab)How to fix?
Upgrade Minimos:latest argocd-3.3-compat to version 3.3.15-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream argocd-3.3-compat package and not the argocd-3.3-compat package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
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.
References
- https://www.cve.org/CVERecord?id=CVE-2026-77459
- https://github.com/advisories/GHSA-fmxq-cgp8-87wp
- https://osv.dev/vulnerability/MINI-gq75-x9mx-vj4c
- https://osv.dev/vulnerability/CVE-2026-77459
- https://github.com/argoproj/argo-cd/commit/1149cdc6e932208c4402183cc3d7b7485239940c
- https://github.com/argoproj/argo-cd/commit/4bc8085b0a6d2296b849539d3d09fc7be7a4a511
- https://github.com/argoproj/argo-cd/commit/7f0a05834b05103d69d7c150e1ee36541b314696
- https://github.com/argoproj/argo-cd/commit/d5dd7019ee65be8895133fe4df554e28074242c4
- https://github.com/argoproj/argo-cd/releases/tag/v3.3.15
- https://github.com/argoproj/argo-cd/releases/tag/v3.4.10
- https://github.com/argoproj/argo-cd/releases/tag/v3.5.4
- https://github.com/argoproj/argo-cd/releases/tag/v3.6.0-rc2
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-fmxq-cgp8-87wp