CVE-2026-35568 is a DNS rebinding vulnerability in the official MCP Java SDK server implementation, affecting the io.modelcontextprotocol.sdk:mcp-core package prior to version 1.0.0. The flaw is in the server transport layer handling incoming HTTP/JSON-RPC connections: the SDK did not enforce mandatory origin validation on inbound requests as required by the MCP specification. As a result, an attacker can abuse a victim’s browser through DNS rebinding to send unauthorized cross-origin requests to a locally bound or network-private MCP server. Those requests are processed as if they originated from a trusted, locally running MCP-connected AI agent, allowing arbitrary tool invocations exposed by the server.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.