Memory exhaustion in Model Context Protocol Java SDK HTTP transports
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-770.
Summary
The io.modelcontextprotocol.sdk:mcp artifact is affected from 0.8.0 before 0.13.0, and mcp-core from 0.13.0 before 0.18.4, from 1.0.0 before 1.1.4, and from 2.0.0-M1 before 2.0.1. The Servlet-based SSE, Streamable HTTP and Stateless transports read request bodies into memory without a size limit (CWE-770). An unauthenticated remote client can stream an arbitrarily large POST body until the Java process exhausts its heap.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Update io.modelcontextprotocol.sdk:mcp to 0.13.0, and io.modelcontextprotocol.sdk:mcp-core to 0.18.4, 1.1.4 or 2.0.1.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
- Fix · CNA io.modelcontextprotocol.sdk:mcp (modelcontextprotocol) Fixed in 0.13.0
- Fix · CNA io.modelcontextprotocol.sdk:mcp-core (modelcontextprotocol) Fixed in 0.18.4, 1.1.4, 2.0.1
Vendor assessments
Timeline
- 2026-10-15 Threatist record created from CVE-2026-108395
- 2026-10-16 Priority changed: LOW → MEDIUM
- 2026-11-06 Affected versions changed · Red Hat
- 2026-11-06 CVSS score added · Red Hat
References
Other 8
- https://github.com/modelcontextprotocol/java-sdk/security/advisories/GHSA-4x8c-5vv7-973f
- https://github.com/modelcontextprotocol/java-sdk/commit/1499df22c7023aa257223143a5dcf5b1db7ef80d
- https://github.com/modelcontextprotocol/java-sdk/commit/6a41dedaa0625551582d8247e5a4d78eae1131b2
- https://github.com/modelcontextprotocol/java-sdk/commit/8c0fdd1b1f76adba3ce7945d29f73fa2ddc66598
- https://github.com/modelcontextprotocol/java-sdk/commit/9e4d5fa827b6ba69457f5fd93573184789528efa
- https://github.com/modelcontextprotocol/java-sdk/releases/tag/v0.18.4
- https://github.com/modelcontextprotocol/java-sdk/releases/tag/v1.1.4
- https://github.com/modelcontextprotocol/java-sdk/releases/tag/v2.0.1
More MLflow vulnerabilities
- TI-2026-46366 Server-side request forgery in mlflow KEVCVSS 3.1CRITICAL 9.3
- TI-2023-03518 Absolute Path Traversal in mlflow/mlflow CVSS 3.1CRITICAL 10.0
- TI-2023-01113 Path Traversal: '\..\filename' in mlflow/mlflow CVSS 3.1CRITICAL 9.8
- TI-2025-31759 Redis Lua Use-After-Free may lead to remote code execution CVSS 3.1CRITICAL 10.0
- TI-2026-81527 Code execution via scorer deserialization in MLflow servers CVSS 3.1CRITICAL 9.8
- TI-2025-14028 Command Injection in mlflow/mlflow CVSS 3.1CRITICAL 10.0
Sources
- CVE-2026-108395 · CVE Program
- CVE-2026-108395 · NVD
- FIRST EPSS
- CVE-2026-108395 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences