How severe is CVE-2025-10193?

No CVSS score has been assigned to CVE-2025-10193 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-10193?

CVE-2025-10193 affects the following packages: mcp-neo4j-cypher (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2025-10193?

Update mcp-neo4j-cypher to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10193 is resolved across your whole dependency graph.

How do I detect CVE-2025-10193 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mcp-neo4j-cypher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-10193 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-10193 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-10193 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-10193?

CVE-2025-10193 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-10193?

CVE-2025-10193 is classified as CWE-346 (CWE-346). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-10193 published, and has it been updated?

CVE-2025-10193 was published on September 11, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2025-10193 — mcp-neo4j-cypher

Fix: neo4j-contrib/mcp-neo4j#165

CVE-2025-10193 is a CWE-346 vulnerability in mcp-neo4j-cypher. A fix is available for mcp-neo4j-cypher — see the affected versions and patch details below.

Neo4j Cypher MCP server is vulnerable to DNS rebinding attacks

Also known asGHSA-vcqx-v2mg-7chxPYSEC-2026-1620

Published

Sep 11, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-10193.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍mcp-neo4j-cypher

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Patches

CORS Middleware added to Cypher MCP server v0.4.0 that blocks all web-based access by default.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`mcp-neo4j-cypher`	≥ 0.2.2&&< 0.4.0	0.4.0`pip install --upgrade 'mcp-neo4j-cypher==0.4.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mcp-neo4j-cypher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mcp-neo4j-cypher to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10193 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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. ### Patches CORS Middleware added to Cypher MCP server v0.4.0 that blocks all web-based access by default. ### Workarounds If you cannot upgrade to v0.4.0 and above, use stdio mode. ### References [Vendor Advisory](https://neo4j.com/secu

O3 Security · Impact-Aware SCA

Is CVE-2025-10193 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works