EUVD-2026-19954

Description

### Summary The java-sdk contains a DNS rebinding vulnerability. This vulnerability allows an attacker to access a locally or network-private java-sdk MCP server via a victims browser that is either local, or network adjacent. This allows an attacker to make any tool call to the server as if they were a locally running MCP connected AI agent. ### Details Prior to 1.0.0 no Origin header validation was occurring, in violation of the MCP specification. [Base Protocol > Transports: 2.0.1 Security Warning](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#security-warning): > 1: Servers MUST validate the Origin header on all incoming connections to prevent DNS rebinding attacks. When the web server serving HTTP traffic to the MCP server does not perform standard CORS checks, a DNS rebinding attack is possible. Some default server configurations and frameworks come with embedded `Origin` header validation. MCP servers built using those are not vulnerable to this issue. For example, the following are NOT vulnerable: - Spring AI ### Impact Any developer connecting to a malicious website can inadvertently allow an attacker to make tool calls to local or private-network MCP servers. ### Workarounds Users can mitigate this risk by: 1. Running the MCP server behind a reverse proxy (like Nginx or HAProxy) configured to strictly validate the `Host` and `Origin` headers. 2. Using a framework that inherently enforces strict CORS and Origin validation (such as Spring AI).

Priority Score