cve.bz

CVE-2026-55797 argoproj argo-cd: OS Command Injection

8.8 highEPSS 2.2%Fix available

High (8.8) in argoproj argo-cd. EPSS 2.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/argoproj/argo-cd/v3 3.3.15, 3.4.10, 3.5.4.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
2.2% (unchanged from 2.2% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 83rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-55797 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-55797?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-55797?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-55797 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
argoproj argo-cd>= 2.11.0, <= 2.14.21
argoproj argo-cd>= 3.0.0, < 3.3.15
argoproj argo-cd>= 3.4.0, < 3.4.10
argoproj argo-cd>= 3.5.0, < 3.5.4
argoproj argo-cd= 3.6.0-rc1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-j6cw-g6p4-7hchGogithub.com/argoproj/argo-cd/v2>=2.11.0 <=2.14.21no fix published
GHSA-j6cw-g6p4-7hchGogithub.com/argoproj/argo-cd/v3>=3.0.0 <3.3.153.3.15
GHSA-j6cw-g6p4-7hchGogithub.com/argoproj/argo-cd/v3>=3.4.0 <3.4.103.4.10
GHSA-j6cw-g6p4-7hchGogithub.com/argoproj/argo-cd/v3>=3.5.0 <3.5.43.5.4
GHSA-j6cw-g6p4-7hchGogithub.com/argoproj/argo-cd/v3>=3.6.0-rc1 <3.6.0-rc23.6.0-rc2
GO-2026-6701Gogithub.com/argoproj/argo-cdall versionsno fix published
GO-2026-6701Gogithub.com/argoproj/argo-cd/v2>=2.11.0no fix published
GO-2026-6701Gogithub.com/argoproj/argo-cd/v3>=3.0.0 <3.3.15
>=3.4.0 <3.4.10
>=3.5.0 <3.5.4
>=3.6.0-rc1 <3.6.0-rc2
3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1SUSE-SU-2026:24730-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity because authenticated users with permissions to manage repository definitions can achieve arbitrary code execution inside the Argo CD repository server pod and access sensitive infrastructure credentials. In Red Hat OpenShift GitOps environments, successful exploitation requires authorization to add or modify repository configurations or credential templates, restricting the threat to privileged accounts. Although arbitrary commands execute within the repo-server pod context, standard OpenShift security context constraints and container boundaries prevent direct privilege escalation to the underlying cluster node.

ProductPackageStateAdvisory
Red Hat OpenShift GitOps 1.20openshift-gitops-1/gitops-rhel9:1792361748Fixed 2026-10-26RHSA-2026:90323
Red Hat OpenShift GitOps 1.21openshift-gitops-1/gitops-rhel9:1792368118Fixed 2026-10-26RHSA-2026:90337
Red Hat Openshift Data Foundation 4odf4/odf-multicluster-rhel9-operatorAffected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-agent-rhel9Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-image-updater-rhel9Affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-rhel9Affected
Red Hat OpenShift GitOpsopenshift-gitops-1/gitops-rhel9-operatorAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-55797.

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON