← Back
CVE-2026-35402
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.
AI summary snake-internal / snake-material-v2
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. CVSS score: ?/10.
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.
❓ What is the problem
**A vulnerability** (CWE-284) exists in mcp-neo4j-cypher. Attackers reach the vulnerable code path via ``read_only`` without authentication.
📍 Affected scope
mcp-neo4j-cypher — . Attack surface: `read_only` / `CALL` / `apoc.import.file.enabled` / `false`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.6.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mcp-neo4j-cypher to 0.6.0ステージング環境で 0.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
mcp-neo4j-cypher
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.6.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-35402
- advisory https://github.com/advisories/GHSA-x3cv-r3g3-fpg9
- package https://github.com/neo4j-contrib/mcp-neo4j
- package https://pypi.org/project/mcp-neo4j-cypher
- web https://github.com/neo4j-contrib/mcp-neo4j/security/advisories/GHSA-x3cv-r3g3-fpg9
- web https://github.com/neo4j-contrib/mcp-neo4j/releases/tag/mcp-neo4j-cypher-v0.6.0