CVE-2026-35402 | neo4j-contrib mcp-neo4j up to 0.5.x APOC CALL read_only access control (GHSA-x3cv-r3g3-fpg9)
VulDBArchived Apr 18, 2026✓ Full text saved
A vulnerability identified as critical has been detected in neo4j-contrib mcp-neo4j up to 0.5.x . This affects the function read_only of the component APOC CALL Handler . This manipulation causes improper access controls. The identification of this vulnerability is CVE-2026-35402 . It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358130 · CVE-2026-35402 · GHSA-X3CV-R3G3-FPG9
NEO4J-CONTRIB MCP-NEO4J UP TO 0.5.X APOC CALL READ_ONLY ACCESS CONTROL
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
6.0 $0-$5k 2.44+
Summaryinfo
A vulnerability labeled as critical has been found in neo4j-contrib mcp-neo4j up to 0.5.x. This vulnerability affects the function read_only of the component APOC CALL Handler. Such manipulation leads to access control. This vulnerability is referenced as CVE-2026-35402. It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.
Detailsinfo
A vulnerability, which was classified as critical, has been found in neo4j-contrib mcp-neo4j up to 0.5.x. Affected by this issue is the function read_only of the component APOC CALL Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-35402 since 04/02/2026. The exploitation is known to be easy. The attack may be launched remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
Upgrading to version 0.6.0 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Productinfo
Type
Artificial Intelligence Software
Vendor
neo4j-contrib
Name
mcp-neo4j
Version
0.1
0.2
0.3
0.4
0.5
Website
Product: https://github.com/neo4j-contrib/mcp-neo4j/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Access control
CWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: mcp-neo4j 0.6.0
Timelineinfo
04/02/2026 CVE reserved
04/17/2026 +15 days Advisory disclosed
04/17/2026 +0 days VulDB entry created
04/17/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: GHSA-x3cv-r3g3-fpg9
Status: Confirmed
CVE: CVE-2026-35402 (🔒)
GCVE (CVE): GCVE-0-2026-35402
GCVE (VulDB): GCVE-100-358130
Entryinfo
Created: 04/17/2026 23:51
Changes: 04/17/2026 23:51 (71)
Complete: 🔍
Cache ID: 99:902:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸