ArgoCD's repo server has Uncontrolled Resource Consumption vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2024-29893: 0.97% estimated exploitation activity in the next 30 days; percentile 62.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

29 Mar 2024, 19:04 UTC

Last modified by the source

29 Mar 2024, 19:04 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jhwx-mhww-rgc3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-29893

Advisory: ArgoCD's repo server has Uncontrolled Resource Consumption vulnerability
IDs: CVE-2024-29893, GHSA-jhwx-mhww-rgc3
Record: https://patchnext.com/advisories/cve-2024-29893 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/argoproj/argo-cd/v2 2.10.5, 2.9.10, 2.8.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected >= 2.4.0, < 2.8.14; >= 2.9.0, < 2.9.10; >= 2.10.0, < 2.10.5; fixed in 2.10.5, 2.8.14, 2.9.10

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jhwx-mhww-rgc3 (GitHub-reviewed advisory GHSA-jhwx-mhww-rgc3 lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=2.4.0 =2.9.0 =2.10.0 <2.10.5)

Commands are suggestions: review each one before running it.