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.
CVE-2026-55797
HIGHPre-NVD 8.88.8Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.5% (74th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%The EG Score, 8.8 of 10.Exploitation1.6% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 1.5%
- EPSS %ILE
- 74th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 9, 2026
Last Modified
October 9, 2026
Advisory Details (8)
Auto-updated Oct 9, 2026Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available
v3.6.0-rc2
Patch available: argoproj/argo-cd v3.6.0-rc2 (pre-release)
https://github.com/argoproj/argo-cd/releases/tag/v3.6.0-rc2GitHub release Patch Available
v3.5.4
Patch available: argoproj/argo-cd v3.5.4
https://github.com/argoproj/argo-cd/releases/tag/v3.5.4GitHub release Patch Available
v3.4.10
Patch available: argoproj/argo-cd v3.4.10
https://github.com/argoproj/argo-cd/releases/tag/v3.4.10GitHub release Patch Available
v3.3.15
Patch available: argoproj/argo-cd v3.3.15
https://github.com/argoproj/argo-cd/releases/tag/v3.3.15GitHub commit
commit 9b27aeb1a4fb (argoproj/argo-cd)
Fix landed in argoproj/argo-cd commit 9b27aeb1a4fb — awaiting tagged release
https://github.com/argoproj/argo-cd/commit/9b27aeb1a4fb15d11a0f01cad65dea1fdfc60205GitHub commit
commit 1e3ddd0b7250 (argoproj/argo-cd)
Fix landed in argoproj/argo-cd commit 1e3ddd0b7250 — awaiting tagged release
https://github.com/argoproj/argo-cd/commit/1e3ddd0b7250aa23f489956b5fab8c13d0493a9fGitHub pull request
feat(reposerver): Support for socks5 proxy for Git URLs using SSH scheme
Fix merged in argoproj/argo-cd PR #15864 on 2024-01-09 — awaiting tagged release
https://github.com/argoproj/argo-cd/pull/15864GitHub advisoryMentions a patch (unverified)
Command injection via a repository proxy URL on SSH Git repositories · Advisory · argoproj/argo-cd · GitHub
https://github.com/argoproj/argo-cd/security/advisories/GHSA-j6cw-g6p4-7hchVendor Advisories for CVE-2026-55797(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/argoproj/argo-cd/v2 | — |
| — |
| github.com/argoproj/argo-cd/v3 | 3.6.0-rc1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-12 15:55 UTCEG score recompute
- 2026-10-11 19:38 UTCEG score recompute
- 2026-10-11 16:53 UTCEG score recompute
- 2026-10-11 14:16 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-10 20:39 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.5% · 74th percentile
- 2026-10-09 18:34 UTCEG score recompute
- 2026-10-09 17:34 UTCEG score recompute
- 2026-10-09 16:54 UTCEG score recomputeFirst assessed: 8.8 HIGH
- 2026-10-09 16:53 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownGo:github.com/argoproj/argo-cd/v3
Frequently asked(5)
What is CVE-2026-55797?
CVE-2026-55797 is a high-severity vulnerability; its CVE record was published on October 9, 2026. 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…
When was the CVE record for CVE-2026-55797 published?
The CVE record for CVE-2026-55797 was published on October 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55797 actively exploited?
CVE-2026-55797 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55797?
CVE-2026-55797 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55797?
A fix for CVE-2026-55797 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55797 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55797
Is Your Infrastructure Affected by CVE-2026-55797?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.