CVE-2024-29893: ArgoCD's repo server has Uncontrolled Resource Consumption vulnerability
Impact All versions of ArgoCD starting from v2.4 have a bug where the ArgoCD repo-server component is vulnerable to a Denial-of-Service attack vector. Specifically, it's possible to crash the repo server component through an out of memory error by pointing it to a malicious Helm registry. The loadRepoIndex() function in the ArgoCD's helm package, does not limit the size nor time while fetching the data.
Published Mar 29, 2024
Affected packages
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.4.0, < 2.8.14
- Fixed in
- 2.8.14
- Check
go list -m github.com/argoproj/argo-cd/v2
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.9.0, < 2.9.10
- Fixed in
- 2.9.10
- Check
go list -m github.com/argoproj/argo-cd/v2
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.10.0, < 2.10.5
- Fixed in
- 2.10.5
- Check
go list -m github.com/argoproj/argo-cd/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
All versions of ArgoCD starting from v2.4 have a bug where the ArgoCD repo-server component is vulnerable to a Denial-of-Service attack vector. Specifically, it's possible to crash the repo server component through an out of memory error by pointing it to a malicious Helm registry. The loadRepoIndex() function in the ArgoCD's helm package, does not limit the size nor time while fetching the data. It fetches it and creates a byte slice from the retrieved data in one go. If the registry is implemented to push data continuously, the repo server will keep allocating memory until it runs out of it.
Patches
A patch for this vulnerability has been released in the following Argo CD versions:
v2.10.5 v2.9.10 v2.8.14
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 Jakub Ciolek
The Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue
Credited to jake-ciolek.
References
- https://github.com/argoproj/argo-cd/security/advisories/GHSA-jhwx-mhww-rgc3
- https://nvd.nist.gov/vuln/detail/CVE-2024-29893
- https://github.com/argoproj/argo-cd/commit/14f681e3ee7c38731943b98f92277e88a3db109d
- https://github.com/argoproj/argo-cd/commit/36b8a12a38f8d92d55bffc81deed44389bf6eb59
- https://github.com/argoproj/argo-cd/commit/3e5a878f6e30d935fa149723ea2a2e93748fcddd
- https://github.com/advisories/GHSA-jhwx-mhww-rgc3
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
