How severe is GHSA-63qx-x74g-jcr7?

GHSA-63qx-x74g-jcr7 has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-63qx-x74g-jcr7?

GHSA-63qx-x74g-jcr7 affects the following packages: github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd (Go). Ecosystems affected: Go.

How do I fix GHSA-63qx-x74g-jcr7?

Update github.com/argoproj/argo-cd/v2 to 2.1.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-63qx-x74g-jcr7 is resolved across your whole dependency graph.

How do I detect GHSA-63qx-x74g-jcr7 in my Go dependencies?

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

How do I mitigate GHSA-63qx-x74g-jcr7 if there is no patch (or I can't update yet)?

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.

Is GHSA-63qx-x74g-jcr7 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-63qx-x74g-jcr7, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-63qx-x74g-jcr7?

GHSA-63qx-x74g-jcr7 has an EPSS (Exploit Prediction Scoring System) score of 2.7%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-63qx-x74g-jcr7?

GHSA-63qx-x74g-jcr7 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-63qx-x74g-jcr7 published, and has it been updated?

GHSA-63qx-x74g-jcr7 was published on February 7, 2022 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

Path traversal and dereference of symlinks in Argo CDGHSA-63qx-x74g-jcr7

HIGHFix: argoproj/argo-cd@78c2084

GHSA-63qx-x74g-jcr7 is a high-severity (CVSS 7.7) Path Traversal vulnerability in github.com/argoproj/argo-cd/v2. 2 public exploit references exist, so weaponization risk is real. A fix is available for github.com/argoproj/argo-cd/v2 — see the affected versions and patch details below.

Also known asCVE-2022-24348GO-2022-0304

Published

Feb 7, 2022

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-63qx-x74g-jcr7 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v2🐹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 versions of Argo CD are vulnerable to a path traversal bug that allows to pass arbitrary values files to be consumed by Helm charts.

Additionally, it is possible to craft special Helm chart packages containing value files that are actually symbolic links, pointing to arbitrary files outside the repository's root directory.

If an attacker with permissions to create or update Applications knows or can guess the full path to a file containing valid YAML, they can create a malicious Helm chart to consume that YAML as values files, thereby gaining access to data they would otherwise have no access to.

The impact can especially become critical in environments that make use of encrypted value files (e.g. using plugins with git-crypt or SOPS) containing sensitive or confidential data, and decrypt these secrets to disk before rendering the Helm chart.

Also, because any error message from helm template is passed back to the user, and these error messages are quite verbose, enumeration of files on the repository server's file system is possible.

Patches

A patch for this vulnerability has been released in the following Argo CD versions:

v2.3.0
v2.2.4
v2.1.9

We urge users of Argo CD to update their installation to one of the fixed versions as listed above.

Workarounds

No workaround for this issue.

References

For more information

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

Credits

The path traversal vulnerability was discovered and reported by Moshe Zioni, VP Security Research, Apiiro.

During the development of a fix for the path traversal vulnerability, the Argo CD team discovered the related issue with symbolic links.

The Argo CD team would like to thank Moshe Zioni for the responsible disclosure, and the constructive discussions during handling this issue!

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-cd/v2`	all versions	2.1.9`go get github.com/argoproj/argo-cd/v2@v2.1.9`
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.2.0&&< 2.2.4	2.2.4`go get github.com/argoproj/argo-cd/v2@v2.2.4`
🐹Go	`github.com/argoproj/argo-cd`	all versions	2.1.9`go get github.com/argoproj/argo-cd@v2.1.9`

Affected Products

1 product · 2 configurations

Application

argo cdargoproj

≥ 2.2.0 && < 2.2.4

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Argo CD before 2.1.9 and 2.2.x before 2.2.4 allows directory traversal r…

apiiro.comNVDFeb 2022

Argo CD before 2.1.9 and 2.2.x before 2.2.4 allows directory traversal r…

github.comNVDFeb 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/argoproj/argo-cd/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/argoproj/argo-cd/v2 to 2.1.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-63qx-x74g-jcr7 is resolved across your whole dependency graph.
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

Product	Fixed in	Advisory
Red Hat OpenShift GitOps 1.2	`openshift-gitops-1/applicationset-rhel8:v1.2.2-3`	RHSA-2022:0580
Red Hat OpenShift GitOps 1.3	`openshift-gitops-1/applicationset-rhel8:v1.3.3-2`	RHSA-2022:0476
Red Hat OpenShift GitOps 1.3	`openshift-gitops-1/applicationset-rhel8:v1.3.4-1`	RHSA-2022:0682
Red Hat OpenShift GitOps 1.4	`openshift-gitops-1/applicationset-rhel8:v1.4.2-3`	RHSA-2022:0477

Frequently Asked Questions

### Impact All versions of Argo CD are vulnerable to a path traversal bug that allows to pass arbitrary values files to be consumed by Helm charts. Additionally, it is possible to craft special Helm chart packages containing value files that are actually symbolic links, pointing to arbitrary files outside the repository's root directory. If an attacker with permissions to create or update Applications knows or can guess the full path to a file containing valid YAML, they can create a malicious Helm chart to consume that YAML as values files, thereby gaining access to data they would otherw

O3 Security · Impact-Aware SCA

Is GHSA-63qx-x74g-jcr7 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-22Path Traversal

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Feb 7, 2022

First exploit

Feb 9, 2022

2 days after disclosure — rapid exploitation

Last updated

Jul 8, 2026

Identifiers

GHSA-63qx-x74g-jcr7

GO-2022-0304

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webapiiro.com Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

This CVE is high severity; 6 of 8 other CVEs affecting v2 are rated as high or higher (top: critical).

CVE-2026-45738CVE-2025-59531CVE-2025-55191CVE-2025-59538CVE-2025-59537CVE-2025-55190CVE-2025-47933CVE-2025-23216

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026