mediumresolved

MCP Java handler failures expose internal exception details

Unexpected handler exceptions are returned to the peer with their underlying stack and causes. A connected client or server can therefore learn implementation details from failures in the opposite side.

Unexpected handler exceptions are returned to the peer with their underlying stack and causes. A connected client or server can therefore learn implementation details from failures in the opposite side.

This is a maintainer-documented vulnerability disclosure. The advisory lists affected ranges: io.modelcontextprotocol.sdk:mcp-core >= 0.11.0, 0 < 0.18.5; io.modelcontextprotocol.sdk:mcp-core >= 1.0.0, < 1.1.5; io.modelcontextprotocol.sdk:mcp-core >= 2.0.0, < 2.1.0. Patched release lines: io.modelcontextprotocol.sdk:mcp-core 0.18.5; io.modelcontextprotocol.sdk:mcp-core 1.1.5; io.modelcontextprotocol.sdk:mcp-core 2.1.0. Consult the specific advisory for configuration requirements and branch coverage.

Takeaway

Use a patched release on a supported branch and verify the relevant browser, process or session boundary. Keep untrusted MCP endpoints and imported configurations outside privileged runtime contexts.

Sources

mcpjavaghsa-w83x-jw8h-w4rj