# Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server Advisory record · `GHSA-6gcg-hp2x-q54h` - **Identifiers:** `GHSA-6gcg-hp2x-q54h` · `CVE-2022-24904` · `GO-2022-0453` - **State:** Confirmed - **Severity:** CVSS 4.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-59](https://cwe.mitre.org/data/definitions/59.html) · [CWE-61](https://cwe.mitre.org/data/definitions/61.html) - **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [CWE-61](https://agentprime.io/advisories/tag/cwe-61.md) - **Published:** 23 May 2022 - **Updated:** 21 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 23 May 2022, 21:13 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/argoproj/argo-cd/v2` (Go): affected `<2.1.15 || >=2.2.0, <2.2.9 || >=2.3.0, <2.3.4`; fixed in `2.1.15`, `2.2.9`, `2.3.4` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Argo CD (github.com/argoproj/argo-cd/v2) versions before 2.1.15, from 2.2.0 before 2.2.9, and from 2.3.0 before 2.3.4 are affected. A user with write access to a repository used by a directory-type Application can commit a symlink to an out-of-bounds file and read its contents from the repo-server. Upgrade to 2.1.15, 2.2.9, 2.3.4, or later; if upgrading is not possible on a 2.3.x release, disable the built-in Jsonnet/directory tool by setting jsonnet.enable to false. Written 1 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 - 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.012, the 67th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:11 UTC: First seen by agentprime - 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6gcg-hp2x-q54h) ## Sources - [GitHub Advisory Database: GHSA-6gcg-hp2x-q54h](https://github.com/advisories/GHSA-6gcg-hp2x-q54h) - [OSV: GHSA-6gcg-hp2x-q54h](https://osv.dev/vulnerability/GHSA-6gcg-hp2x-q54h) - - - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .