CVE-2026-55797: 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.
Published Oct 9, 2026
Affected packages
github.com/argoproj/argo-cd/v2
- Ecosystem
- Go
- Affected
- >= 2.11.0, <= 2.14.21
- Fixed in
- No patched version yet
- Check
go list -m github.com/argoproj/argo-cd/v2
github.com/argoproj/argo-cd/v3
- Ecosystem
- Go
- Affected
- >= 3.0.0, < 3.3.15
- Fixed in
- 3.3.15
- Check
go list -m github.com/argoproj/argo-cd/v3
github.com/argoproj/argo-cd/v3
- Ecosystem
- Go
- Affected
- >= 3.4.0, < 3.4.10
- Fixed in
- 3.4.10
- Check
go list -m github.com/argoproj/argo-cd/v3
github.com/argoproj/argo-cd/v3
- Ecosystem
- Go
- Affected
- >= 3.5.0, < 3.5.4
- Fixed in
- 3.5.4
- Check
go list -m github.com/argoproj/argo-cd/v3
github.com/argoproj/argo-cd/v3
- Ecosystem
- Go
- Affected
- = 3.6.0-rc1
- Fixed in
- 3.6.0-rc2
- Check
go list -m github.com/argoproj/argo-cd/v3
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
--proxyflag 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
Credited to kamil-sawicki, yuvalelarat, cherez0ff, McCaulay, ria-labs-security, parameter-ai-security, zwindler.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-77459
Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
critical9.9No fixOct 15, 2026CVE-2026-45737
Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations
medium6.3May 19, 2026CVE-2026-45738
Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation
high7.3No fixMay 19, 2026CVE-2026-42880
ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction
critical9.6May 7, 2026CVE-2025-55191
Repository Credentials Race Condition Crashes Argo CD Server
medium6.5Sep 30, 2025CVE-2025-59531
Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload
high7.5No fixSep 30, 2025
