# CVE-2023-40026: Path traversal allows leaking out-of-bound Helm charts from Argo CD repo-server


- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 27 Sep 2023
- **Updated:** 20 Sep 2024
- **Also known as:** GHSA-6jqw-jwf5-rp8h, GO-2023-2085

## What is CVE-2023-40026?

CVE-2023-40026 is a medium-severity vulnerability in Argoproj Argo Cd, published on 27 Sep 2023. 

### Official description

Argo CD is a declarative continuous deployment framework for Kubernetes. 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. This issue was fixed in Argo CD 2.3 and subsequent versions by randomizing Helm paths. 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2023-40026?

6 open source packages ship an affected version, including github.com/argoproj/argo-cd and github.com/argoproj/argo-cd/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/argoproj/argo-cd` | Go | All versions | None |
| `github.com/argoproj/argo-cd` | Go | All versions to 1.8.7 | None |
| `github.com/argoproj/argo-cd` | Go | All versions to 1.8.7 | None |
| `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.3.0 |
| `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.3.0 |
| `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.3.0 |

Products: Argoproj Argo Cd.

## How do I fix CVE-2023-40026?

Upgrade to a fixed version.

## Is CVE-2023-40026 being exploited?

There is no known exploitation of CVE-2023-40026 in the wild and no public exploit code.

## Other vulnerabilities in Argoproj Argo Cd

- [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0)
- [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0)
- [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9)
- [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9)
- [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-40026 and fix it if it is affected.

What it is: CVE-2023-40026 is a medium-severity vulnerability in Argoproj Argo Cd, published on 27 Sep 2023. 
Exploitation: There is no known exploitation of CVE-2023-40026 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/argoproj/argo-cd (Go): affected all versions; no fix listed
- github.com/argoproj/argo-cd (Go): affected all versions up to 1.8.7; no fix listed
- github.com/argoproj/argo-cd (Go): affected all versions up to 1.8.7; no fix listed
- github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.3.0
- github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.3.0
- github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-40026/ (Markdown: https://insights.sbomify.com/CVE-2023-40026/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-40026
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-40026
- OSV: https://osv.dev/vulnerability/CVE-2023-40026

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-40026/
Summaries are generated and may contain mistakes; the official description above is the record.