CVE-2026-35402: mcp-neo4j · Improper Access Control
Affects mcp-neo4jSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 0.6.0 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade mcp-neo4j and neo4j-contrib/mcp-neo4j to 0.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| neo4j-contribmcp-neo4j | Affected
| Fixed in
|
GitHubneo4j-contrib/mcp-neo4jpkg:github/neo4j-contrib/mcp-neo4jOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade mcp-neo4j to version 0.6.0 or later, where this access control bypass issue is fixed. Patch status is not explicitly confirmed beyond the fix in version 0.6.0, so check vendor sources for the latest remediation guidance.
Description
mcp-neo4j-cypher is an MCP server for executing Cypher queries against Neo4j databases. In versions prior to 0.6.0, the read_only mode enforcement can be bypassed using APOC CALL procedures, potentially allowing unauthorized write operations or server-side request forgery. This issue is fixed in version 0.6.0.