Is CVE-2026-55797 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55797 being exploited in the wild.

How severe is CVE-2026-55797?

High severity, with a CVSS score of 8.8, published 9 October 2026.

Which products and versions are affected?

Argo Project Argo CD v2.11.0 through v3.2; not v2.10.20 and earlier; github.com/argoproj/argo-cd (Go) SEMVER:introduced=0; github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=2.11.0, SEMVER:introduced=2.11.0,last_affected=2.14.21; github.com/argoproj/argo-cd/v3 (Go) SEMVER:introduced=3.0.0,fixed=3.3.15, SEMVER:introduced=3.0.0,fixed=3.3.15,introduced=3.4.0,fixed=3.4.10,introduced=3.5.0,fixed=3.5.4,introduced=3.6.0-rc1,fixed=3.6.0-rc2.

How is CVE-2026-55797 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-55797?

Check whether you run Argo Project Argo CD, github.com/argoproj/argo-cd (Go), github.com/argoproj/argo-cd/v2 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55797: Argo CD repo-server command injection via SSH proxy URL

CVE-2026-55797 · Severity: high · CVSS 8.8 · Published 2026-10-09

Argo CD is a continuous deployment tool that synchronizes applications from Git repositories. A flaw allows attackers with repository creation or update permissions to inject shell commands through a crafted SOCKS5 proxy URL on SSH repositories, enabling arbitrary command execution on the repo-server and potential theft of stored Git, Helm, and OCI credentials. All versions from 2.11.0 through 3.2 are affected; versions 2.10.20 and earlier are not vulnerable.

Technologies: Argo Project Argo CD, github.com/argoproj/argo-cd (Go), github.com/argoproj/argo-cd/v2 (Go), github.com/argoproj/argo-cd/v3 (Go). Vendors: Argo Project, Go.

Quick answers

Is CVE-2026-55797 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55797 being exploited in the wild.
How severe is CVE-2026-55797?: High severity, with a CVSS score of 8.8, published 9 October 2026.
Which products and versions are affected?: Argo Project Argo CD v2.11.0 through v3.2; not v2.10.20 and earlier; github.com/argoproj/argo-cd (Go) SEMVER:introduced=0; github.com/argoproj/argo-cd/v2 (Go) SEMVER:introduced=2.11.0, SEMVER:introduced=2.11.0,last_affected=2.14.21; github.com/argoproj/argo-cd/v3 (Go) SEMVER:introduced=3.0.0,fixed=3.3.15, SEMVER:introduced=3.0.0,fixed=3.3.15,introduced=3.4.0,fixed=3.4.10,introduced=3.5.0,fixed=3.5.4,introduced=3.6.0-rc1,fixed=3.6.0-rc2.
Is there a fix for CVE-2026-55797?: Yes. github.com/argoproj/argo-cd/v3 (Go): upgrade to 3.3.15, 3.6.0-rc2 or later. Until then: Do not grant repository create or update permissions to untrusted users, including project-scoped repository access. Do not set proxy fields on SSH repositories or credential templates that match SSH repositories; review existing repository and credential-template Secrets for unexpected proxy values. HTTPS Git repositories with HTTP proxies are not affected and do not require proxy removal.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-09"},{"kind":"patched","at":"2026-10-09","note":"Patches released in v3.6.0-rc2, v3.5.4, v3.4.10, v3.3.15"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55797 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-55797?: Check whether you run Argo Project Argo CD, github.com/argoproj/argo-cd (Go), github.com/argoproj/argo-cd/v2 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/argoproj/argo-cd/v3 (Go): upgrade to 3.3.15, 3.6.0-rc2 or later
```
go get github.com/argoproj/argo-cd/v3@v3.6.0-rc2
```

Do not grant repository create or update permissions to untrusted users, including project-scoped repository access. Do not set proxy fields on SSH repositories or credential templates that match SSH repositories; review existing repository and credential-template Secrets for unexpected proxy values. HTTPS Git repositories with HTTP proxies are not affected and do not require proxy removal.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-09"},{"kind":"patched","at":"2026-10-09","note":"Patches released in v3.6.0-rc2, v3.5.4, v3.4.10, v3.3.15"}]

Technical details

The vulnerability is a shell command injection in repo-server's SSH repository proxy handling. When cloning or fetching an SSH Git repository with a proxy URL, the proxy host and port are unsanitized and directly embedded in an SSH ProxyCommand executed via shell. An attacker who can create or update repositories (via direct repository add, project-scoped permissions, or credential templates) can inject shell metacharacters in the proxy host field to break out of the command context. The fix stops passing proxy host/port through shell, properly quoting or parameterizing them instead.

Affected products

Argo Project Argo CD v2.11.0 through v3.2; not v2.10.20 and earlier

Identifiers

CVE-2026-55797
BIT-ARGO-CD-2026-55797
GHSA-j6cw-g6p4-7hch
GO-2026-6701

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.