Vulnerability in mcp-neo4j-cypher (CVE-2026-35402)
Summary
Vulnerability in mcp-neo4j-cypher (CVE-2026-35402). Risk of unauthorized operations or information disclosure. Exploitable via read_only. Mitigation: upgrade to 0.6.0 or later.
Original description
The description as published by the source.
Summary
The read_only mode in mcp-neo4j-cypher versions prior to 0.6.0 can be bypassed using CALL procedures.
Details
Impact
The enforcing of read_only mode in vulnerable versions could be bypassed by certain APOC procedures.
Patches
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.
Notes
Impacts for server-side request forgery vulnerabilities may depend on both the configuration of the vulnerable system as well as the presence of other systems in the environment that could be accessed as part of exploitation.
Recommended hardening
- Limit the apoc procedures to what's required
- Manage data loading privileges
- Don't relax the default settings without compensating controls
apoc.import.file.enabledisfalseby defaultapoc.import.file.use_neo4j_configistrueby default to restrict file imports to the import folder
Credits
We want to publicly recognise the contribution of Yotam Perkal from Pluto Security.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35402 has been found in mcp-neo4j-cypher.
Attackers can target a specific entry point like read_only over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mcp-neo4j-cypher to 0.6.0 or later.
If unsure, ask your IT team or search "mcp-neo4j-cypher CVE-2026-35402" on the vendor's site.
CVE-2026-35402 (mcp-neo4j-cypher) — CWE-284
Attack surface: read_only / CALL / apoc.import.file.enabled / false
Patched: 0.6.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in mcp-neo4j-cypher. Attackers reach the vulnerable code path via read_only.
Check the vendor advisory for the affected versions of mcp-neo4j-cypher. Attack surface: read_only / CALL / apoc.import.file.enabled / false.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.6.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mcp-neo4j-cypher' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mcp-neo4j-cypher' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mcp-neo4j-cypherを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mcp-neo4j-cypher to 0.6.0ステージング環境で 0.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com