github.com/argoproj/argo-cd/v2
Affected
- introduced
2.11.0, last affected2.14.21(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: BIT-argo-cd-2026-55797, CVE-2026-55797, GO-2026-6701
Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URL
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:
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.
--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
For more information
High Basis: The source's own band: HIGH
2.11.0, last affected 2.14.21 (semver)None listed
No fixed version is listed.
3.0.0, fixed 3.3.15 (semver)3.3.15
3.3.15go get github.com/argoproj/argo-cd/[email protected]3.4.0, fixed 3.4.10 (semver)3.4.10
3.4.10go get github.com/argoproj/argo-cd/[email protected]3.5.0, fixed 3.5.4 (semver)3.5.4
3.5.4go get github.com/argoproj/argo-cd/[email protected]3.6.0-rc1, fixed 3.6.0-rc2 (semver)3.6.0-rc2
3.6.0-rc2go get github.com/argoproj/argo-cd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0