CVE-2023-40026

Workarounds

User's still using Argo CD 2.3 or below are advised to update to a supported version. If this is not possible, disabling Helm chart rendering, or using an additional repo-server for each Helm chart would prevent possible exploitation.

References

https://github.com/argoproj/argo-cd/security/advisories/GHSA-63qx-x74g-jcr7

For more information

If you have any questions or comments about this advisory:

• Open an issue in example link to repo
• Email us at example email address

In Argo CD versions prior to 2.3 (starting at least in v0.1.0, but likely in any version using Helm before 2.3), using a specifically-crafted Helm file could reference external Helm charts handled by the same repo-server to leak values, or files from the referenced Helm Chart. This was possible because Helm paths were predictable.

The vulnerability worked by adding a Helm chart that referenced Helm resources from predictable paths. Because the paths of Helm charts were predictable and available on an instance of repo-server, it was possible to reference and then render the values and resources from other existing Helm charts regardless of permissions. While generally, secrets are not stored in these files, it was nevertheless possible to reference any values from these charts.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2023-40026 has a CVSS score of 5.0 (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.3.0); upgrading removes the vulnerable code path.

Kodem intelligence

This issue was fixed in Argo CD 2.3 and subsequent versions by randomizing Helm paths.

1. What is CVE-2023-40026? CVE-2023-40026 is a medium-severity path traversal vulnerability in github.com/argoproj/argo-cd (go), affecting versions <= 1.8.7. It is fixed in 2.3.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2023-40026? CVE-2023-40026 has a CVSS score of 5.0 (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 packages are affected by CVE-2023-40026?
   • github.com/argoproj/argo-cd (go) (versions <= 1.8.7)
   • github.com/argoproj/argo-cd/v2 (go) (versions < 2.3.0)
4. Is there a fix for CVE-2023-40026? Yes. CVE-2023-40026 is fixed in 2.3.0. Upgrade to this version or later.
5. Is CVE-2023-40026 exploitable, and should I be worried? Whether CVE-2023-40026 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-40026 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-40026? Upgrade github.com/argoproj/argo-cd/v2 to 2.3.0 or later.