CVE-2025-66414

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-200274 (ENISA EUVD) · GHSA-w48q-cv73-mx4w (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
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: 0.5%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. Prior to 1.24.0, The Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default for HTTP-based servers. When an HTTP-based MCP server is run on localhost without authentication with StreamableHTTPServerTransport or SSEServerTransport and has not enabled enableDnsRebindingProtection, a malicious website could exploit DNS rebinding to bypass same-origin policy restrictions and send requests to the local MCP server. This could allow an attacker to invoke tools or access resources exposed by the MCP server on behalf of the user in those limited circumstances. Note that running HTTP-based MCP servers locally without authentication is not recommended per MCP security best practices. This issue does not affect servers using stdio transport. This vulnerability is fixed in 1.24.0.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

December 2, 2025

Last Modified

October 18, 2026

Advisory Details (2)

Auto-updated Aug 8, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

DNS Rebinding Protection Disabled by Default in Model Context Protocol TypeScript SDK for Servers Running on Localhost · Advisory · modelcontextprotocol/typescript-sdk · GitHub

https://github.com/modelcontextprotocol/typescript-sdk/security/advisories/GHSA-w48q-cv73-mx4w
GitHub commit Patch Available

commit 09623e2aa504 (modelcontextprotocol/typescript-sdk)

Patch available: modelcontextprotocol/typescript-sdk @modelcontextprotocol/node@2.0.0-beta.3 (contains commit 09623e2aa504)

https://github.com/modelcontextprotocol/typescript-sdk/commit/09623e2aa5044f9e9da62c73d820a8250b9d97ed

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@modelcontextprotocol/sdk @ 1.24.0 (fixes < 1.24.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@modelcontextprotocol/sdk—
  • every version up to 1.24.0: fixed in 1.24.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 95 of 201 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-66414?
CVE-2025-66414 is a high-severity vulnerability; its CVE record was published on December 2, 2025. MCP TypeScript SDK is the official TypeScript SDK for Model Context Protocol servers and clients. Prior to 1.24.0, The Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default for HTTP-based servers. When an HTTP-based MCP server is run on localhost without…
When was the CVE record for CVE-2025-66414 published?
The CVE record for CVE-2025-66414 was published on December 2, 2025. 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 18, 2026; the record at its source may have been updated since.
Is CVE-2025-66414 actively exploited?
CVE-2025-66414 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-66414?
CVE-2025-66414 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-66414?
A fix for CVE-2025-66414 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-66414

Explore →

Is Your Infrastructure Affected by CVE-2025-66414?

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

Book a Demo →Browse All CVEs