CVE-2026-55580

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th 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
Elevated
8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

mcp-shell is an MCP server for running shell commands securely, auditably, and on demand. Prior to 0.6.0, config.go initializes Security.Enabled to false, and when MCP_SHELL_SEC_CONFIG_FILE is unset, main.go starts the documented bare-binary deployment without a security policy. SecurityValidator.validateCommand in security.go then short-circuits and allows every command supplied to the shell_exec MCP tool, so an LLM connected over stdio can execute unrestricted OS commands as the mcp-shell process user. The README from-source installation and MCP client configuration omit MCP_SHELL_SEC_CONFIG_FILE, making the insecure state the documented default. This issue is fixed in version 0.6.0.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
55
EG Risk 55/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)
Severity86% × 45%
The EG Score, 8.6 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available

v0.6.0 — secure mode by default

Patch available: sonirico/mcp-shell v0.6.0

https://github.com/sonirico/mcp-shell/releases/tag/v0.6.0
GitHub commit Patch Available

commit f31377fce6ec (sonirico/mcp-shell)

Patch available: sonirico/mcp-shell v0.6.0 (contains commit f31377fce6ec)

https://github.com/sonirico/mcp-shell/commit/f31377fce6ec31114e5a4398c0e5270552bce09f
GitHub pull request Patch Available

fix: secure mode by default + keep interpreters out of the allowlist

Patch available: sonirico/mcp-shell v0.6.0 (PR #16 merged 2026-06-14)

https://github.com/sonirico/mcp-shell/pull/16
GitHub advisoryMentions a patch (unverified)

mcp-shell — Security Disabled by Default in Bare-Binary Deploy Path + Shell Interpreter in Secure-Mode Allowlist · Advisory · sonirico/mcp-shell · GitHub

https://github.com/sonirico/mcp-shell/security/advisories/GHSA-f5pj-2738-996m

Vendor Advisories for CVE-2026-55580(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/sonirico/mcp-shell—
  • every version up to 0.6.0: fixed in 0.6.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 55× 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.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-12 15:41 UTCEG score recompute
  3. 2026-10-11 19:39 UTCEG score recompute
  4. 2026-10-11 16:54 UTCEG score recompute
  5. 2026-10-11 14:17 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-10 12:02 UTCEG score recompute
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-09 04:23 UTCEG score recompute
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-08 03:16 UTCEG score recompute
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-07 01:10 UTCEG score recompute
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-06 02:32 UTCEG score recompute
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-05 02:21 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-03 16:38 UTCEG score recompute
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-02 18:22 UTCEG score recompute
  23. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-01 20:05 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 64 more
  1. 2026-09-30 20:15 UTCEG score recompute
  2. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-09-30 06:46 UTCEG score recompute
  4. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-09-29 08:37 UTCEG score recompute
  6. 2026-09-28 21:29 UTCEG score recompute
  7. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-09-27 20:40 UTCEG score recompute
  9. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-09-26 22:05 UTCEG score recompute
  11. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-09-24 20:24 UTCEG score recompute
  13. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-09-23 22:08 UTCEG score recompute
  15. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-09-22 23:52 UTCEG score recompute
  17. 2026-09-22 01:36 UTCEG score recompute
  18. 2026-09-21 03:19 UTCEG score recompute
  19. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-09-19 17:44 UTCEG score recompute
  21. 2026-09-19 06:36 UTCEG score recompute
  22. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-09-17 21:08 UTCEG score recompute
  24. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-16 21:34 UTCEG score recompute
  26. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  27. 2026-09-16 09:33 UTCEG score recompute
  28. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  29. 2026-09-15 11:12 UTCEG score recompute
  30. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-09-14 01:28 UTCEG score recompute
  32. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-09-12 16:04 UTCEG score recompute
  34. 2026-09-11 17:48 UTCEG score recompute
  35. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  36. 2026-09-10 19:32 UTCEG score recompute
  37. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  38. 2026-09-09 01:14 UTCEG score recompute
  39. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  40. 2026-09-07 19:13 UTCEG score recompute
  41. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  42. 2026-09-06 20:24 UTCEG score recompute
  43. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  44. 2026-09-05 21:56 UTCEG score recompute
  45. 2026-09-04 23:41 UTCEG score recompute
  46. 2026-09-04 12:32 UTCEG score recompute
  47. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  48. 2026-09-02 15:56 UTCEG score recompute
  49. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  50. 2026-09-01 17:32 UTCEG score recompute
  51. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  52. 2026-08-30 20:51 UTCEG score recompute
  53. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  54. 2026-08-30 09:44 UTCEG score recompute
  55. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  56. 2026-08-29 00:15 UTCEG score recompute
  57. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  58. 2026-08-28 01:06 UTCEG score recompute
  59. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  60. 2026-08-26 15:41 UTCEG score recompute
  61. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  62. 2026-08-25 16:23 UTCEG score recompute
  63. 2026-08-25 15:50 UTCEG score recomputeFirst assessed: 8.6 HIGH
  64. 2026-08-25 15:49 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/sonirico/mcp-shell

Frequently asked(5)

What is CVE-2026-55580?
CVE-2026-55580 is a high-severity vulnerability; its CVE record was published on August 25, 2026. mcp-shell is an MCP server for running shell commands securely, auditably, and on demand. Prior to 0.6.0, config.go initializes Security.Enabled to false, and when MCPSHELLSECCONFIGFILE is unset, main.go starts the documented bare-binary deployment without a security policy.…
When was the CVE record for CVE-2026-55580 published?
The CVE record for CVE-2026-55580 was published on August 25, 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55580 actively exploited?
CVE-2026-55580 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55580?
CVE-2026-55580 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55580?
A fix for CVE-2026-55580 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55580 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-55580

Explore →

Is Your Infrastructure Affected by CVE-2026-55580?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs