Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2022-24904: 1.15% estimated exploitation activity in the next 30 days; percentile 66.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact All unpatched versions of Argo CD starting with v0.7.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive files from Argo CD's repo-server. A malicious Argo CD user with write access for a repository which is (or may be) used in a directory-type Application may commit a symlink which points to an out-of-bounds file. If the target file is a valid JSON or YAML manifest file, and the resource is allowed in the Application, the attacker can read the contents of that manifest file. (In versions <2.3.2, <2.2.8, and <2.1.14, the attacker may read the files contents even if the resource is not allowed in the Application). If the target file is valid JSON but is not a manifest file, the attacker may read the contents of the file. If the target file is not valid JSON or YAML, the attacker may read partial file contents (usually just the first character of the file). Sensitive files which could be leaked include manifest…

Published by the source

23 May 2022, 21:13 UTC

Last modified by the source

17 Apr 2023, 19:07 UTC

Source last checked

26 Oct 2026, 14:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6gcg-hp2x-q54h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-24904

Advisory: Symlink following allows leaking out-of-bound manifests and JSON files from Argo CD repo-server
IDs: CVE-2022-24904, GHSA-6gcg-hp2x-q54h
Record: https://patchnext.com/advisories/cve-2022-24904 (revision 1, source checked 26 Oct 2026, 14:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/argoproj/argo-cd/v2 2.3.4, 2.2.9, 2.1.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected < 2.1.15; >= 2.2.0, < 2.2.9; >= 2.3.0, < 2.3.4; fixed in 2.3.4, 2.1.15, 2.2.9

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6gcg-hp2x-q54h (GitHub-reviewed advisory GHSA-6gcg-hp2x-q54h lists affected ranges: Go github.com/argoproj/argo-cd/v2 >=0 =2.2.0 =2.3.0 <2.3.4)

Commands are suggestions: review each one before running it.