Java-SDK has a DNS Rebinding Vulnerability
CVE-2026-35568 · GHSA-8jxr-pr72-r468 · published 2026-04-07 · updated 2026-04-08
- Severity
- High
- CVSS score
- 7.6
- Chance of exploitation (EPSS)
- 0.16%
- Fixed in
- 1.0.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
Any developer connecting to a malicious website can inadvertently allow an attacker to make tool calls to local or private-network MCP servers.
Upgrade io.modelcontextprotocol.sdk:mcp-core to 1.0.0 or later.
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).
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| io.modelcontextprotocol.sdk:mcp-core | Maven | < 1.0.0 | 1.0.0 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- MediumMCP Java SDK has a Hardcoded Wildcard CORS (Access-Control-Allow-Origin: *)io.modelcontextprotocol.sdk:mcp-core, io.modelcontextprotocol.sdk:mcp-core, io.modelcontextprotocol.sdk:mcp-core
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.