← Back
CVE-2025-10193
Vulnerability in mcp-neo4j-cypher (CVE-2025-10193)
Summary
vulnerability in mcp-neo4j-cypher (CVE-2025-10193). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.4.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-10193** has been found in mcp-neo4j-cypher.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade mcp-neo4j-cypher to **0.4.0** or later.
If unsure, ask your IT team or search "mcp-neo4j-cypher CVE-2025-10193" on the vendor's site.
CVE-2025-10193 (mcp-neo4j-cypher) — CWE-346 /
Patched: `0.4.0` — apply immediately
Workaround: If you cannot upgrade to v0.4.0 and above, use stdio mode.
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-346) exists in mcp-neo4j-cypher.
📍 Affected scope
mcp-neo4j-cypher — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.4.0**.
🛡️ Workaround
Workaround: If you cannot upgrade to v0.4.0 and above, use stdio mode.
🔍 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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
If you cannot upgrade to v0.4.0 and above, use stdio mode.パッチが適用されるまでの応急処置として、If you cannot upgrade to v0.4.0 and above, use stdio mode. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade mcp-neo4j-cypher to 0.4.0ステージング環境で 0.4.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.2.2"},{"fixed":"0.4.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-10193
- advisory https://github.com/advisories/GHSA-vcqx-v2mg-7chx
- 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-vcqx-v2mg-7chx
- web https://github.com/neo4j-contrib/mcp-neo4j/pull/165
- web https://github.com/neo4j-contrib/mcp-neo4j/commit/5b9fbdda6401668d7aa006daf7e644805c067c15
- web https://github.com/neo4j-contrib/mcp-neo4j/releases/tag/mcp-neo4j-cypher-v0.4.0
- web https://neo4j.com/security/cve-2025-10193