CVE-2026-108395

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th 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

Also known asEUVD-2026-101503 (ENISA EUVD)Source: ENISA EUVD

7.5EG
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: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The Model Context Protocol Java SDK is the official Java SDK for Model Context Protocol servers and clients. From version 0.8.0 through 0.12.0 in the io.modelcontextprotocol.sdk:mcp artifact, from 0.13.0 through 0.18.3 and 1.0.0 through 1.1.3 in io.modelcontextprotocol.sdk:mcp-core, and from mcp-core 2.0.0-M1 through 2.0.0, the Servlet-based SSE, Streamable HTTP, and Stateless server transports read an HTTP request body into memory without enforcing a maximum size. An unauthenticated remote client able to reach an affected transport can stream an arbitrarily large POST body, including with chunked transfer encoding, until the Java process exhausts its heap and becomes unavailable. Authentication, Origin or Host validation, or an upstream request-size limit can reject the request before the vulnerable read. The maintained mcp-core lines are fixed in versions 0.18.4, 1.1.4, and 2.0.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 partial (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
49th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; 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 partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 14, 2026

Last Modified

October 16, 2026

Advisory Details (8)

Auto-updated Oct 14, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Unbounded request-body reads in mcp-core HTTP server transports allow remote denial of service (CWE-770) · Advisory · modelcontextprotocol/java-sdk · GitHub

https://github.com/modelcontextprotocol/java-sdk/security/advisories/GHSA-4x8c-5vv7-973f
GitHub release Patch Available

v2.0.1

Patch available: modelcontextprotocol/java-sdk v2.0.1

https://github.com/modelcontextprotocol/java-sdk/releases/tag/v2.0.1
GitHub release Patch Available

v1.1.4

Patch available: modelcontextprotocol/java-sdk v1.1.4

https://github.com/modelcontextprotocol/java-sdk/releases/tag/v1.1.4
GitHub release Patch Available

v0.18.4

Patch available: modelcontextprotocol/java-sdk v0.18.4

https://github.com/modelcontextprotocol/java-sdk/releases/tag/v0.18.4
GitHub commit Patch Available

commit 9e4d5fa827b6 (modelcontextprotocol/java-sdk)

Patch available: modelcontextprotocol/java-sdk v1.1.4 (contains commit 9e4d5fa827b6)

https://github.com/modelcontextprotocol/java-sdk/commit/9e4d5fa827b6ba69457f5fd93573184789528efa
GitHub commit Patch Available

commit 8c0fdd1b1f76 (modelcontextprotocol/java-sdk)

Patch available: modelcontextprotocol/java-sdk v0.18.4 (contains commit 8c0fdd1b1f76)

https://github.com/modelcontextprotocol/java-sdk/commit/8c0fdd1b1f76adba3ce7945d29f73fa2ddc66598
GitHub commit Patch Available

commit 6a41dedaa062 (modelcontextprotocol/java-sdk)

Patch available: modelcontextprotocol/java-sdk v2.0.1 (contains commit 6a41dedaa062)

https://github.com/modelcontextprotocol/java-sdk/commit/6a41dedaa0625551582d8247e5a4d78eae1131b2
GitHub commit Patch Available

commit 1499df22c702 (modelcontextprotocol/java-sdk)

Patch available: modelcontextprotocol/java-sdk v0.13.0 (contains commit 1499df22c702)

https://github.com/modelcontextprotocol/java-sdk/commit/1499df22c7023aa257223143a5dcf5b1db7ef80d

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 29× 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-11-02 16:43 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-29 15:14 UTCEG score recompute
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-25 14:54 UTCEG score recompute
  12. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-23 03:45 UTCEG score recompute
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-18 05:07 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-10-16 16:10 UTCEG score recompute
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-10-14 20:33 UTCEG score recompute
Show 4 more
  1. 2026-10-14 19:39 UTCEG score recompute
  2. 2026-10-14 18:27 UTCEG score recompute
  3. 2026-10-14 17:56 UTCEG score recomputeFirst assessed: 7.5 HIGH
  4. 2026-10-14 17:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-108395?
CVE-2026-108395 is a high-severity vulnerability; its CVE record was published on October 14, 2026. The Model Context Protocol Java SDK is the official Java SDK for Model Context Protocol servers and clients. From version 0.8.0 through 0.12.0 in the io.modelcontextprotocol.sdk:mcp artifact, from 0.13.0 through 0.18.3 and 1.0.0 through 1.1.3 in io.modelcontextprotocol.sdk:mcp-core, and from…
When was the CVE record for CVE-2026-108395 published?
The CVE record for CVE-2026-108395 was published on October 14, 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 16, 2026; the record at its source may have been updated since.
Is CVE-2026-108395 actively exploited?
CVE-2026-108395 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-108395?
CVE-2026-108395 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108395?
A fix for CVE-2026-108395 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-108395?

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