Neo4j Labs MCP Servers: SSRF and Data Modification via read_only Mode Bypass Through CALL Procedures
CVE-2026-35402 · GHSA-x3cv-r3g3-fpg9 · published 2026-04-17 · updated 2026-04-24
- Severity
- Low
- CVSS score
- 2.3
- Chance of exploitation (EPSS)
- 0.25%
- Fixed in
- 0.6.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
The enforcing of read_only mode in vulnerable versions could be bypassed by certain APOC procedures.
Upgrade mcp-neo4j-cypher to 0.6.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
v0.6.0 release hardened the checks around the mode. The only way to guarantee the server actions is to limit the permissions of the db credentials available to the server.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| mcp-neo4j-cypher | PyPI | < 0.6.0 | 0.6.0 |
1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.
- io.github.neo4j-contrib/mcp-neo4j-cyphermcp-neo4j-cypher@0.5.1
- 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
- HighNeo4j Cypher MCP server is vulnerable to DNS rebindingmcp-neo4j-cypher
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.