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. 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
Other sources
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 2.11.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, the Argo CD repo-server is vulnerable to command injection when it clones, tests, or fetches an SSH Git repository configured with a proxy URL. The proxy host and port are embedded in an SSH ProxyCommand that is executed through a shell without neutralizing shell metacharacters. A user who can create or update a repository or repository credential template can supply a crafted proxy host to execute commands in the repo-server and access its Git, Helm, and OCI credentials. This issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/argoproj/argo-cd/v3to a version that resolves this vulnerability.Fixed in 3.6.0-rc2 - Upgrade
Upgrade
go/github.com/argoproj/argo-cd/v3to a version that resolves this vulnerability.Fixed in 3.5.4 - Upgrade
Upgrade
go/github.com/argoproj/argo-cd/v3to a version that resolves this vulnerability.Fixed in 3.4.10 - Upgrade
Upgrade
go/github.com/argoproj/argo-cd/v3to a version that resolves this vulnerability.Fixed in 3.3.15 - Upgrade
Upgrade
Argo CDto a version that resolves this vulnerability.Fixed in 3.3.15 - Upgrade
Upgrade
Argo CDto a version that resolves this vulnerability.Fixed in 3.4.10 - Upgrade
Upgrade
Argo CDto a version that resolves this vulnerability.Fixed in 3.5.4 - Upgrade
Upgrade
Argo CDto a version that resolves this vulnerability.Fixed in 3.6.0-rc2 - Configuration
Do not set a proxy on an SSH repository or on a credential template that matches SSH repositories.
Argo CD SSH repositories and credential templates proxy = unset - Compensating control
Do not grant repository create or update permissions to untrusted users, including project-scoped repository access.
- Operational
Review existing repository and credential-template Secrets for unexpected proxy values.
Event History
Frequently Asked Questions
Which deployments are not affected by this issue?
Argo CD v2.10.20 and earlier are not affected. Versions from v2.11.0 onward are affected, including all currently supported releases.
Which repository configurations can trigger the vulnerable code path?
The repository must use SSH and have a proxy configured. HTTP, HTTPS, and SOCKS5 proxy URLs can all reach the vulnerable SSH ProxyCommand path when configured on an SSH repository; HTTPS Git repositories do not build this command.
Who could use this to execute commands in the repo-server?
An attacker needs permission to create or update a repository or repository credential template and must be able to set its proxy. This includes project-scoped repository permissions, use of argocd repo add --proxy, and access to configure a repository Secret.
Can a repository credential template expand the exposure?
Yes. A credential template's proxy setting applies to every matching SSH repository, so a malicious proxy configured in a template can affect multiple matching repositories.