# Path traversal allows leaking out-of-bound files from Argo CD repo-server in github.com/argoproj/argo-cd

Advisory record · `GHSA-h6h5-6fmq-rh28`

- **Identifiers:** `GHSA-h6h5-6fmq-rh28` · `CVE-2022-24731` · `GO-2022-0358`
- **State:** Confirmed
- **Severity:** CVSS 6.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 21 Aug 2024
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

[Published by the maintainers](https://github.com/argoproj/argo-cd/security/advisories/GHSA-h6h5-6fmq-rh28) · 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 21 Aug 2024, 14:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/argoproj/argo-cd` (Go): affected `>=1.5.0`; no fixed version yet
- `github.com/argoproj/argo-cd/v2` (Go): affected `<2.1.11 || >=2.2.0, <2.2.6 || >=2.3.0-rc1, <2.3.0`; fixed in `2.1.11`, `2.2.6`, `2.3.0`

## Machine-written summary

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

> Path traversal in the Argo CD repo-server lets an attacker leak files outside the intended directory. The source gives few details on the access an attacker needs. Upgrade github.com/argoproj/argo-cd/v2 to 2.1.11, 2.2.6, or 2.3.0, matching your release line. No fixed version is listed for github.com/argoproj/argo-cd.

Written 10 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

- 6.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0096, the 62nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 23 Mar 2022, 13:38 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/argoproj/argo-cd/security/advisories/GHSA-h6h5-6fmq-rh28)

## Sources

- [GitHub Advisory Database: GHSA-h6h5-6fmq-rh28](https://github.com/advisories/GHSA-h6h5-6fmq-rh28)
- [OSV: GHSA-h6h5-6fmq-rh28](https://osv.dev/vulnerability/GHSA-h6h5-6fmq-rh28)
- <https://github.com/argoproj/argo-cd/security/advisories/GHSA-h6h5-6fmq-rh28>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-24731>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h6h5-6fmq-rh28>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h6h5-6fmq-rh28/>. Everything for agents: <https://agentprime.io/llms.txt>.
