NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Path traversal allows leaking out-of-bound files from Argo CD repo-serverGHSA-h6h5-6fmq-rh28

MEDIUM

GHSA-h6h5-6fmq-rh28 is a medium-severity (CVSS 6.8) Path Traversal vulnerability in github.com/argoproj/argo-cd. A fix is available for github.com/argoproj/argo-cd — see the affected versions and patch details below.

Also known asCVE-2022-24731GO-2022-0358
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-h6h5-6fmq-rh28.

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk
0.00%0.49%0.97%1.46%0.3%1.0%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐹github.com/argoproj/argo-cd🐹github.com/argoproj/argo-cd🐹github.com/argoproj/argo-cd

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 way to avoid the vulnerability is to upgrade.

To mitigate the problem, you can

References

For more information

Open an issue in the Argo CD issue tracker or discussions Join us on Slack in channel #argo-cd

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/argoproj/argo-cd≥ 1.5.0&&< 2.1.112.1.11go get github.com/argoproj/argo-cd@v2.1.11
🐹Gogithub.com/argoproj/argo-cd≥ 2.2.0&&< 2.2.62.2.6go get github.com/argoproj/argo-cd@v2.2.6
🐹Gogithub.com/argoproj/argo-cd≥ 2.3.0-rc1&&< 2.3.02.3.0go get github.com/argoproj/argo-cd@v2.3.0

Affected Products

1 product · 6 configurations
Application
argo cdargoproj
≥ 2.2.0 && < 2.2.6
1 version
2.3.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-cd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/argoproj/argo-cd to 2.1.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h6h5-6fmq-rh28 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
Red Hat OpenShift GitOps 1.2openshift-gitops-1/argocd-rhel8:v1.2.3-3RHSA-2022:1039
Red Hat OpenShift GitOps 1.3openshift-gitops-1/argocd-rhel8:v1.3.5-4RHSA-2022:1040
Red Hat OpenShift GitOps 1.3openshift-gitops-1/argocd-rhel8:v1.3.6-3RHSA-2022:1042
Red Hat OpenShift GitOps 1.4openshift-gitops-1/argocd-rhel8:v1.4.4-6RHSA-2022:1041

Frequently Asked Questions

### 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](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions) 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
O3 Security · Impact-Aware SCA

Is GHSA-h6h5-6fmq-rh28 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Path traversal allows leaking out-of-bound files from Argo…