CVE-2023-40584

CVE-2023-40584 is a medium-severity uncontrolled resource consumption vulnerability in github.com/argoproj/argo-cd/v2 (go), affecting versions >= 2.4.0, < 2.6.15. It is fixed in 2.6.15, 2.7.14, 2.8.3.

Summary

Workarounds

The only way to completely resolve the issue is to upgrade.

Mitigations

Configure RBAC (Role-Based Access Control) and provide access for configuring applications only to a limited number of administrators. These administrators should utilize trusted and verified Helm charts.

For more information

If you have any questions or comments about this advisory:

Credits

This vulnerability was found & reported by GE Vernova, Amit Laish.

The Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue

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, the said component extracts a user-controlled tar.gz file without validating the size of its inner files. As a result, a malicious, low-privileged user can send a malicious tar.gz file that exploits this vulnerability to the repo-server, thereby harming the system's functionality and availability. Additionally, the repo-server is susceptible to another vulnerability due to the fact that it does not check the extracted file permissions before attempting to delete them. Consequently, an attacker can craft a malicious tar.gz archive in a way that prevents the deletion of its inner files when the manifest generation process is completed.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2023-40584 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.6.15, 2.7.14, 2.8.3); upgrading removes the vulnerable code path.

Affected versions

github.com/argoproj/argo-cd/v2 (>= 2.4.0, < 2.6.15) github.com/argoproj/argo-cd/v2 (>= 2.7.0, < 2.7.14) github.com/argoproj/argo-cd/v2 (>= 2.8.0, < 2.8.3)

Security releases

github.com/argoproj/argo-cd/v2 → 2.6.15 (go) github.com/argoproj/argo-cd/v2 → 2.7.14 (go) github.com/argoproj/argo-cd/v2 → 2.8.3 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

A patch for this vulnerability has been released in the following Argo CD versions:

  • v2.6.15
  • v2.7.14
  • v2.8.3

Frequently Asked Questions

  1. What is CVE-2023-40584? CVE-2023-40584 is a medium-severity uncontrolled resource consumption vulnerability in github.com/argoproj/argo-cd/v2 (go), affecting versions >= 2.4.0, < 2.6.15. It is fixed in 2.6.15, 2.7.14, 2.8.3. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
  2. How severe is CVE-2023-40584? CVE-2023-40584 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of github.com/argoproj/argo-cd/v2 are affected by CVE-2023-40584? github.com/argoproj/argo-cd/v2 (go) versions >= 2.4.0, < 2.6.15 is affected.
  4. Is there a fix for CVE-2023-40584? Yes. CVE-2023-40584 is fixed in 2.6.15, 2.7.14, 2.8.3. Upgrade to this version or later.
  5. Is CVE-2023-40584 exploitable, and should I be worried? Whether CVE-2023-40584 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2023-40584 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2023-40584?
    • Upgrade github.com/argoproj/argo-cd/v2 to 2.6.15 or later
    • Upgrade github.com/argoproj/argo-cd/v2 to 2.7.14 or later
    • Upgrade github.com/argoproj/argo-cd/v2 to 2.8.3 or later

Other vulnerabilities in github.com/argoproj/argo-cd/v2

CVE-2026-45738CVE-2025-59538CVE-2025-59537CVE-2025-59531CVE-2025-55191

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo