Argo Project Argo CD up to 3.6.0-rc1 repo-server command injection

Summaryinfo

A vulnerability was found in Argo Project Argo CD up to 2.14.21/3.3.14/3.4.9/3.5.3/3.6.0-rc1. It has been classified as very critical. This affects an unknown function of the component repo-server. The manipulation leads to command injection. This vulnerability is listed as CVE-2026-55797. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Argo Project Argo CD up to 2.14.21/3.3.14/3.4.9/3.5.3/3.6.0-rc1. This issue affects an unknown code block of the component repo-server. The manipulation with an unknown input leads to a command injection vulnerability. Using CWE to declare the problem leads to CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-55797 since 06/17/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/09/2026). MITRE ATT&CK project uses the attack technique T1202 for this issue.

Upgrading to version 3.3.15, 3.4.10, 3.5.4 or 3.6.0-rc2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Project Management Software

Vendor

• Argo Project

Name

• Argo CD

Version

• 2.14.0
• 2.14.1
• 2.14.2
• 2.14.3
• 2.14.4
• 2.14.5
• 2.14.6
• 2.14.7
• 2.14.8
• 2.14.9
• 2.14.10
• 2.14.11
• 2.14.12
• 2.14.13
• 2.14.14
• 2.14.15
• 2.14.16
• 2.14.17
• 2.14.18
• 2.14.19
• 2.14.20
• 2.14.21
• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.3.5
• 3.3.6
• 3.3.7
• 3.3.8
• 3.3.9
• 3.3.10
• 3.3.11
• 3.3.12
• 3.3.13
• 3.3.14
• 3.4.0
• 3.4.1
• 3.4.2
• 3.4.3
• 3.4.4
• 3.4.5
• 3.4.6
• 3.4.7
• 3.4.8
• 3.4.9
• 3.5.0
• 3.5.1
• 3.5.2
• 3.5.3
• 3.6.0-rc1

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion