CVE-2026-108395 modelcontextprotocol CVE debrief

Who should care

Defenders responsible for systems using the Model Context Protocol Java SDK, especially those exposed to untrusted or unauthenticated clients, should assess their exposure and prioritize patching or mitigation.

Why it matters

CVE-2026-108395 is a high-severity vulnerability in the Model Context Protocol Java SDK that can lead to memory exhaustion and potential system crashes. Defenders should prioritize patching or mitigating this vulnerability, especially for systems exposed to untrusted or unauthenticated clients. The CVE record and source item provide details on the affected versions and the nature of the vulnerability, but actual exploitation or specific victims are not reported.

• Potential for denial-of-service (DoS) attacks through memory exhaustion.
• Possible system crashes or unavailability due to heap exhaustion.
• Need for verification of affected versions and exposure in the environment.
• Priority for patching or mitigating the vulnerability to prevent exploitation.

Technical summary

The Model Context Protocol Java SDK is vulnerable to memory exhaustion through unbounded request bodies in certain HTTP server transports. This issue affects multiple versions of the io.modelcontextprotocol.sdk:mcp and io.modelcontextprotocol.sdk:mcp-core artifacts. An unauthenticated remote client can exploit this vulnerability by streaming an arbitrarily large POST body until the Java process exhausts its heap and becomes unavailable.

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability, especially for systems exposed to untrusted or unauthenticated clients.

Recommended defensive actions

• Patch or upgrade to a fixed version (0.18.4, 1.1.4, or 2.0.1) for affected io.modelcontextprotocol.sdk:mcp and io.modelcontextprotocol.sdk:mcp-core versions.
• Implement request size limits or authentication mechanisms to mitigate the vulnerability.
• Monitor systems for unusual or large POST requests.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details on the affected versions and the nature of the vulnerability. However, the corpus does not provide information on actual exploitation or specific victims.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.