CVE-2026-85660

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-04. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan mitigationRemediate 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.6%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

cli-mcp-server 0.2.5 contains a command allowlist bypass vulnerability in the _validate_command_with_operators function when ALLOW_SHELL_OPERATORS is enabled. Attackers can use shell command substitution syntax like $(...) or backticks to execute non-allowlisted commands that bypass the ALLOWED_COMMANDS validation check.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
The EG Score, 8.1 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

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

September 4, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 4, 2026
No fix on record yet.
Web page

cli-mcp-server 0.2.5 Command Allowlist Bypass via Shell Substitution | Advisories | VulnCheck

https://www.vulncheck.com/advisories/cli-mcp-server-0.2.5-command-allowlist-bypass-via-shell-substitution
Web page

cli-mcp-server/src/cli_mcp_server/server.py at main · MladenSU/cli-mcp-server · GitHub

https://github.com/MladenSU/cli-mcp-server/blob/main/src/cli_mcp_server/server.py
Web page

GitHub - MladenSU/cli-mcp-server: Command line interface for MCP clients with secure execution and customizable security policies · GitHub

https://github.com/MladenSU/cli-mcp-server
Web page

[Security] Command allowlist bypass via $(...) command substitution · Issue #17 · MladenSU/cli-mcp-server · GitHub

https://github.com/MladenSU/cli-mcp-server/issues/17

Vendor Advisories for CVE-2026-85660(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 142 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 42 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:17 UTCEG score recompute
  2. 2026-10-11 16:34 UTCEG score recompute
  3. 2026-10-11 13:51 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-10 11:23 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  7. 2026-10-09 23:12 UTCEG score recompute
  8. 2026-10-09 23:12 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-09 01:14 UTCEG score recompute
  11. 2026-10-09 01:14 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-07 23:11 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  15. 2026-10-07 02:13 UTCEG score recompute
  16. 2026-10-07 02:13 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-06 14:04 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  19. 2026-10-06 01:55 UTCEG score recompute
  20. 2026-10-06 01:55 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  21. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-10-05 13:45 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  23. 2026-10-05 01:25 UTCEG score recompute
  24. 2026-10-05 01:25 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
Show 75 more
  1. 2026-10-04 13:16 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  2. 2026-10-04 00:57 UTCEG score recompute
  3. 2026-10-04 00:57 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  4. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-10-03 12:37 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  6. 2026-10-02 20:02 UTCEG score recompute
  7. 2026-10-02 20:02 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  8. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-10-02 07:51 UTCEG score recompute
  10. 2026-10-02 07:51 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  11. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-10-01 19:35 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  13. 2026-10-01 07:05 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  14. 2026-09-30 18:56 UTCEG score recompute
  15. 2026-09-30 18:56 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  16. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-09-30 02:43 UTCEG score recompute
  18. 2026-09-30 02:43 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  19. 2026-09-29 04:40 UTCEG score recompute
  20. 2026-09-29 04:40 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  21. 2026-09-28 16:30 UTCEG score recompute
  22. 2026-09-28 16:30 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  23. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-09-28 04:20 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  25. 2026-09-27 16:11 UTCEG score recompute
  26. 2026-09-27 16:11 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  27. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  28. 2026-09-27 04:02 UTCEG score recompute
  29. 2026-09-27 04:02 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  30. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  31. 2026-09-26 15:22 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  32. 2026-09-26 02:27 UTCEG score recompute
  33. 2026-09-26 02:27 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  34. 2026-09-25 09:22 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  35. 2026-09-24 21:13 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  36. 2026-09-24 16:44 UTCEG score recompute
  37. 2026-09-24 16:44 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  38. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  39. 2026-09-24 04:26 UTCEG score recompute
  40. 2026-09-24 04:26 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  41. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  42. 2026-09-23 16:16 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  43. 2026-09-23 04:07 UTCEG score recompute
  44. 2026-09-23 04:07 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  45. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  46. 2026-09-22 15:57 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  47. 2026-09-22 03:48 UTCEG score recompute
  48. 2026-09-22 03:47 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  49. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  50. 2026-09-21 15:38 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  51. 2026-09-21 03:29 UTCEG score recompute
  52. 2026-09-21 03:29 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  53. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  54. 2026-09-20 15:19 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  55. 2026-09-20 03:06 UTCEG score recompute
  56. 2026-09-20 03:06 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  57. 2026-09-19 14:55 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  58. 2026-09-19 02:46 UTCEG score recompute
  59. 2026-09-19 02:45 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  61. 2026-09-18 14:36 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  62. 2026-09-18 02:26 UTCEG score recompute
  63. 2026-09-18 02:26 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  64. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  65. 2026-09-17 14:17 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  66. 2026-09-17 02:07 UTCEG score recompute
  67. 2026-09-17 02:07 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  68. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  69. 2026-09-16 13:57 UTCEG score recompute
  70. 2026-09-16 13:57 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  71. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  72. 2026-09-16 01:25 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  73. 2026-09-15 13:16 UTCEG score recompute
  74. 2026-09-15 13:16 UTCGHSA enrichmentGHSA-wfpw-4v5h-6h32 · GitHub severity CRITICAL · GitHub CVSS 8.1
  75. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85660?
CVE-2026-85660 is a high-severity vulnerability; its CVE record was published on September 4, 2026. cli-mcp-server 0.2.5 contains a command allowlist bypass vulnerability in the validatecommandwithoperators function when ALLOWSHELLOPERATORS is enabled. Attackers can use shell command substitution syntax like $(...) or backticks to execute non-allowlisted commands that bypass the ALLOWED_COMMANDS…
When was CVE-2026-85660 made public?
CVE-2026-85660 was made public on June 5, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 4, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-85660 actively exploited?
CVE-2026-85660 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85660?
CVE-2026-85660 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85660?
No fix for CVE-2026-85660 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-85660 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-85660

Explore →

Is Your Infrastructure Affected by CVE-2026-85660?

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

Book a Demo →Browse All CVEs