CVE-2026-81094

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. A secondary CVSS source baseline 9.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 week
9.1EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The mcp-router CLI served its MCP aggregator on every interface and enforced authentication only when the operator asked for it. The serve command in apps/cli/src/commands/serve.ts defaulted its host to the all-interfaces address on a fixed port, and required a token only when the corresponding flag was supplied, so a default invocation exposed the aggregator, and every MCP server it fronted, to anyone able to reach the port. Release 0.6.3 defaults the host to the loopback address and refuses to start without a token whenever the host it is given is not a loopback address; no earlier release carries either check.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 27, 2026

Last Modified

September 23, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit.
Web page

mcp-router CLI before 0.6.3 Binds the MCP Aggregator to All Interfaces Without Requiring Authentication | Advisories | VulnCheck

https://www.vulncheck.com/advisories/mcp-router-cli-before-0.6.3-binds-the-mcp-aggregator-to-all-interfaces-without-requiring-authentication
Web page

mcp-router/apps/cli/src/commands/serve.ts at v0.6.3 · mcp-router/mcp-router · GitHub

https://github.com/mcp-router/mcp-router/blob/v0.6.3/apps/cli/src/commands/serve.ts#L105
GitHub commit Patch Available

commit 4c4642cfd274 (mcp-router/mcp-router)

Patch available: mcp-router/mcp-router v0.6.3 (contains commit 4c4642cfd274)

https://github.com/mcp-router/mcp-router/commit/4c4642cfd274097ec8b33ecd3047390829c79d35
Web page

GitHub - mcp-router/mcp-router: A Unified MCP Server Management App (MCP Manager). · GitHub

https://github.com/mcp-router/mcp-router

Vendor Advisories for CVE-2026-81094(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 28× in last 7d / 183× 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 317 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 217 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81094?
CVE-2026-81094 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. The mcp-router CLI served its MCP aggregator on every interface and enforced authentication only when the operator asked for it. The serve command in apps/cli/src/commands/serve.ts defaulted its host to the all-interfaces address on a fixed port, and required a token only when the corresponding…
When was CVE-2026-81094 made public?
CVE-2026-81094 was made public on August 26, 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 August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-81094 actively exploited?
CVE-2026-81094 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81094?
CVE-2026-81094 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81094?
A fix for CVE-2026-81094 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81094 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81094?

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

Book a Demo →Browse All CVEs