CVE-2024-31990: Argo CD's API server does not enforce project sourceNamespaces
Impact I can convince the UI to let me do things with an invalid Application. 1. Admin gives me p, michael, applications, , demo/, allow, where demo can just deploy to the demo namespace 2. Admin gives me AppProject dev which reconciles from ns dev-apps 3. Admin gives me p, michael, applications, sync, dev/, allow, i.e. no updating via the UI allowed, gitops-only 4.
Published Apr 15, 2024 · Updated Apr 25, 2024
Affected packages
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.4.0, < 2.8.16
- Fixed in
- 2.8.16
- Check
go list -m github.com/argoproj/argo-cd/v2
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.9.0, < 2.9.12
- Fixed in
- 2.9.12
- Check
go list -m github.com/argoproj/argo-cd/v2
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.10.0, < 2.10.7
- Fixed in
- 2.10.7
- Check
go list -m github.com/argoproj/argo-cd/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
I can convince the UI to let me do things with an invalid Application.
- Admin gives me
p, michael, applications, *, demo/*, allow, wheredemocan just deploy to thedemonamespace - Admin gives me AppProject
devwhich reconciles from nsdev-apps - Admin gives me
p, michael, applications, sync, dev/*, allow, i.e. no updating via the UI allowed, gitops-only - I create an Application called
pwnindev-appswith project dev and sync the app with sources from git - I change the Application’s project to demo via kubectl or gitops (whichever mechanism my admins have given me, because it should be safe)
- I use the UI to edit the resource which should only be mutable via gitops
Patches
A patch for this vulnerability has been released in the following Argo CD versions:
v2.10.7 v2.9.12 v2.8.16
For more information
If you have any questions or comments about this advisory:
Open an issue in the Argo CD issue tracker or discussions Join us on Slack in channel #argo-cd
Credits
This vulnerability was found & reported by @crenshaw-dev (Michael Crenshaw)
The Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue
Credited to crenshaw-dev, pasha-codefresh.
References
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-2gvw-w6fj-7m3c
- https://github.com/argoproj/argo-cd/commit/c514105af739eebedb9dbe89d8a6dd8dfc30bb2c
- https://github.com/argoproj/argo-cd/commit/c5a252c4cc260e240e2074794aedb861d07e9ca5
- https://github.com/argoproj/argo-cd/commit/e0ff56d89fbd7d066e9c862b30337f6520f13f17
- https://nvd.nist.gov/vuln/detail/CVE-2024-31990
- https://github.com/advisories/GHSA-2gvw-w6fj-7m3c
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-77459
Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
critical9.9No fixOct 15, 2026CVE-2026-55797
Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URL
high8.8No fixOct 9, 2026CVE-2026-45738
Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation
high7.3No fixMay 19, 2026CVE-2025-55191
Repository Credentials Race Condition Crashes Argo CD Server
medium6.5Sep 30, 2025CVE-2025-59531
Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload
high7.5No fixSep 30, 2025CVE-2025-59537
argo-cd vulnerable unauthenticated DoS via malformed Gogs webhook payload
high7.5No fixSep 30, 2025
