Path traversal allows leaking out-of-bound files from Argo CD repo-server

Exploitation

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

CVSS

6.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2022-24731: 0.96% estimated exploitation activity in the next 30 days; percentile 61.59 (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 v1.5.0 are 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 other Application's source repositories (potentially decrypted files, if you are using a decryption plugin) or any secrets which have been mounted as files on the repo-server. Patches A patch for this vulnerability has been released in the following Argo CD versions: v2.3.0 v2.2.6 v2.1.11 Workarounds The only certain…

Published by the source

24 Mar 2022, 00:12 UTC

Last modified by the source

7 Aug 2024, 19:46 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h6h5-6fmq-rh28

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

# Patch Next advisory brief: CVE-2022-24731

Advisory: Path traversal allows leaking out-of-bound files from Argo CD repo-server
IDs: CVE-2022-24731, GHSA-h6h5-6fmq-rh28
Record: https://patchnext.com/advisories/cve-2022-24731 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
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 2.3.0, 2.2.6, 2.1.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd: affected >= 1.5.0, < 2.1.11; >= 2.2.0, < 2.2.6; >= 2.3.0-rc1, < 2.3.0; fixed in 2.2.6, 2.3.0, 2.1.11

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd: 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.
- 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-h6h5-6fmq-rh28 (GitHub-reviewed advisory GHSA-h6h5-6fmq-rh28 lists affected ranges: Go github.com/argoproj/argo-cd >=1.5.0 =2.2.0 =2.3.0-rc1 <2.3.0)

Commands are suggestions: review each one before running it.