How severe is GHSA-j6cw-g6p4-7hch?

GHSA-j6cw-g6p4-7hch has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-j6cw-g6p4-7hch?

GHSA-j6cw-g6p4-7hch affects the following packages: github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd/v3 (Go), github.com/argoproj/argo-cd/v3 (Go), github.com/argoproj/argo-cd/v3 (Go), github.com/argoproj/argo-cd/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-j6cw-g6p4-7hch?

No patched version of github.com/argoproj/argo-cd/v2 has shipped for GHSA-j6cw-g6p4-7hch yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-j6cw-g6p4-7hch 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-j6cw-g6p4-7hch if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-j6cw-g6p4-7hch actively exploited in the wild?

No public exploit code has been indexed for GHSA-j6cw-g6p4-7hch yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j6cw-g6p4-7hch?

GHSA-j6cw-g6p4-7hch has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 75th 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-j6cw-g6p4-7hch?

GHSA-j6cw-g6p4-7hch is classified as OS Command Injection (CWE-78). 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-j6cw-g6p4-7hch published, and has it been updated?

GHSA-j6cw-g6p4-7hch was published on October 9, 2026 and was last updated on October 21, 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

Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URLGHSA-j6cw-g6p4-7hch

HIGHFix: argoproj/argo-cd@1e3ddd0

GHSA-j6cw-g6p4-7hch is a high-severity (CVSS 8.8) OS Command Injection vulnerability in github.com/argoproj/argo-cd/v2. A fix is available for github.com/argoproj/argo-cd/v2 — see the affected versions and patch details below.

Also known asBIT-argo-cd-2026-55797CVE-2026-55797GO-2026-6701

Published

Oct 9, 2026

Updated

Oct 21, 2026

Affected

5 pkgs

Patched

4 / 5

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-j6cw-g6p4-7hch.

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-j6cw-g6p4-7hch by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

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

Real-World Exposure

5 pkgs affected

🐹github.com/argoproj/argo-cd/v2🐹github.com/argoproj/argo-cd/v3🐹github.com/argoproj/argo-cd/v3🐹github.com/argoproj/argo-cd/v3🐹github.com/argoproj/argo-cd/v3

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

Argo CD runs a shell command in the repo-server when it clones or fetches an SSH Git repository that has a proxy URL. The proxy host and port are copied into an SSH ProxyCommand. A host that contains shell metacharacters breaks out of that command and runs in the repo-server.

All versions from v2.11.0 onward are affected, including every currently supported release. v2.10.20 and earlier are not. The behavior was introduced in 9b27aeb1a4 (2024-01-09, #15864), the change that added SOCKS5 proxy support for SSH Git URLs, and was first released in v2.11.0.

The repository must use SSH. http, https, and socks5 proxy URLs all take this path when they are set on an SSH repository. An HTTPS Git repository uses the proxy as an HTTP proxy and does not build this command.

Anyone who can create or update a repository or a repository credential template can set the proxy. That includes a project-scoped repository permission, argocd repo add --proxy, and a repository Secret. A credential template applies its proxy to every matching SSH repository that does not have its own credentials. Argo CD runs the command when it tests the repository connection and on later fetches. The process can read other Git, Helm, and OCI credentials stored for the repo-server.

Patches

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

v3.6.0-rc2
v3.5.4
v3.4.10
v3.3.15

The fix stops passing the proxy host and port through a shell.

Argo CD 2.x and 3.0 through 3.2 are out of support and will not receive a patch. Upgrade to a patched 3.3 or newer release.

Workarounds

There is no setting that keeps SSH repository proxies and removes the shell command.

Do not grant repository create or update to untrusted users, including project-scoped repository access. See RBAC resources and project-scoped repositories.
Do not set a proxy on an SSH repository or on a credential template that matches SSH repositories. The proxy field is documented in Configure repositories with proxy. Credential templates are documented in Credential templates. The --proxy flag is documented in argocd repo add.

An HTTPS Git repository with an HTTP proxy does not use this command. Review existing repository and credential-template Secrets for unexpected proxy values.

Credits

The Argo CD team would like to thank @kamil-sawicki, @yuvalelarat, @cherez0ff, @McCaulay, @gehan-psbc, @ria-labs-security, @parameter-ai-security, and @zwindler for responsibly disclosing this issue according to our security reporting guidelines.

References

Introducing commit: 9b27aeb1a4fb15d11a0f01cad65dea1fdfc60205 (#15864), first released in v2.11.0
Configure repositories with proxy

For more information

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

Affected Packages

5 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/argoproj/argo-cd/v2`	≥ 2.11.0	No fix
🐹Go	`github.com/argoproj/argo-cd/v3`	≥ 3.0.0&&< 3.3.15	3.3.15`go get github.com/argoproj/argo-cd/v3@v3.3.15`
🐹Go	`github.com/argoproj/argo-cd/v3`	≥ 3.4.0&&< 3.4.10	3.4.10`go get github.com/argoproj/argo-cd/v3@v3.4.10`
🐹Go	`github.com/argoproj/argo-cd/v3`	≥ 3.5.0&&< 3.5.4	3.5.4`go get github.com/argoproj/argo-cd/v3@v3.5.4`
🐹Go	`github.com/argoproj/argo-cd/v3`	≥ 3.6.0-rc1&&< 3.6.0-rc2	3.6.0-rc2`go get github.com/argoproj/argo-cd/v3@v3.6.0-rc2`

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
No patched version of github.com/argoproj/argo-cd/v2 has shipped for GHSA-j6cw-g6p4-7hch yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact Argo CD runs a shell command in the repo-server when it clones or fetches an SSH Git repository that has a proxy URL. The proxy host and port are copied into an SSH `ProxyCommand`. A host that contains shell metacharacters breaks out of that command and runs in the repo-server. All versions from v2.11.0 onward are affected, including every currently supported release. v2.10.20 and earlier are not. The behavior was introduced in [9b27aeb1a4](https://github.com/argoproj/argo-cd/commit/9b27aeb1a4fb15d11a0f01cad65dea1fdfc60205) (2024-01-09, [#15864](https://github.com/argoproj/argo-cd

O3 Security · Impact-Aware SCA

Is GHSA-j6cw-g6p4-7hch in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-78OS Command Injection

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

argo-cd

8.9/10

Code-Review10/10

Dependency-Update-Tool10/10

Maintained10/10

Vulnerabilities0/10

Branch-Protection8/10

Assessed Oct 23, 2026

Timeline

Disclosed

Oct 9, 2026

Last updated

Oct 21, 2026

Identifiers

GHSA-j6cw-g6p4-7hch

BIT-argo-cd-2026-55797

GO-2026-6701

References

Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

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

CVE-2026-77459CVE-2026-55797CVE-2026-45738CVE-2025-59531CVE-2025-55191CVE-2025-59538CVE-2025-59537CVE-2025-55190

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 21, 2026