Advisory record · GHSA-jhwx-mhww-rgc3

Out of memory crash from malicious Helm registry in github.com/argoproj/argo-cd/v2

CVSS 6.5 MediumEPSS 0.0097 · 62nd percentile

Published by the maintainers · not yet reviewed by GitHub. The argoproj/argo-cd maintainers published this as a GitHub repository advisory; GitHub’s reviewed advisory replaces it here when it arrives.

Published by the argoproj/argo-cd maintainers at 16 Apr 2024, 18:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/argoproj/argo-cd/v2Go>=2.4.0, <2.8.14 || >=2.9.0, <2.9.10 || >=2.10.0, <2.10.52.8.14, 2.9.10, 2.10.5
Identifiers
GHSA-jhwx-mhww-rgc3 · BIT-argo-cd-2024-29893 · CVE-2024-29893 · GO-2024-2667
Weakness (CWE)
CWE-400
Published
16 Apr 2024
Updated
7 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Argo CD (github.com/argoproj/argo-cd/v2) versions 2.4.0 up to 2.8.14, 2.9.0 up to 2.9.10, and 2.10.0 up to 2.10.5 are affected. The source gives few details, but a malicious Helm registry can cause an out-of-memory crash. Upgrade to 2.8.14, 2.9.10, 2.10.5, or a later release.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0097, the 62nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 28 Mar 2024, 20:32 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:54 UTC First seen by agentprime
  3. 31 Oct 2026, 14:54 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.