Summary
Neo4j Cypher MCP server is vulnerable to DNS rebinding
Workarounds
If you cannot upgrade to v0.4.0 and above, use stdio mode.
References
Vendor Advisory
https://www.cve.org/CVERecord?id=CVE-2025-10193
Credits
We want to publicly recognize the contribution of Evan Harris from mcpsec.dev for reporting this issue and following the responsible disclosure policy.
Impact
DNS rebinding vulnerability in Neo4j Cypher MCP server allows malicious websites to bypass Same-Origin Policy protections and execute unauthorised tool invocations against locally running Neo4j MCP instances. The attack relies on the user being enticed to visit a malicious website and spend sufficient time there for DNS rebinding to succeed.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
CORS Middleware added to Cypher MCP server v0.4.0 that blocks all web-based access by default.
Frequently Asked Questions
- What is CVE-2025-10193? CVE-2025-10193 is a high-severity security vulnerability in mcp-neo4j-cypher (pip), affecting versions >= 0.2.2, < 0.4.0. It is fixed in 0.4.0.
- Which versions of mcp-neo4j-cypher are affected by CVE-2025-10193? mcp-neo4j-cypher (pip) versions >= 0.2.2, < 0.4.0 is affected.
- Is there a fix for CVE-2025-10193? Yes. CVE-2025-10193 is fixed in 0.4.0. Upgrade to this version or later.
- Is CVE-2025-10193 exploitable, and should I be worried? Whether CVE-2025-10193 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-10193 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-10193? Upgrade
mcp-neo4j-cypherto 0.4.0 or later.