Authorization Flaw in neo4j (CVE-2026-1497)
Summary
Vulnerability in neo4j (CVE-2026-1497). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.26.22, 2026.2.0 or later.
Original description
The description as published by the source.
Incorrect resolving of namespaces in composite databases in Neo4j Enterprise edition prior to versions 2026.02 and 5.26.22 can lead to the following scenario:
an admin that intends to give a user an access to a remote database constituent "namespace.name" will inadvertently grant access to any local database or remote alias called "name". If such database or alias doesn't exist when the command is run, the privileges will apply if it's created in the future.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-1497 has been found in neo4j.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: upgrade neo4j to 5.26.22, 2026.2.0 or later.
If unsure, ask your IT team or search "neo4j CVE-2026-1497" on the vendor's site.
CVE-2026-1497 (neo4j) — CWE-863 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.26.22, 2026.2.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.
Incorrect authorization (CWE-863) exists in neo4j.
Check the vendor advisory for the affected versions of neo4j.
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.
Update to 5.26.22, 2026.2.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 'neo4j' . 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 'neo4j' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
neo4jを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade neo4j to 5.26.22, 2026.2.0ステージング環境で 5.26.22, 2026.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory neo4j.com
- web nvd.nist.gov
- web github.com