Authorization Flaw in neo4j (CVE-2026-1471)
Summary
Vulnerability in neo4j (CVE-2026-1471). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.26.22, 2026.1.4 or later.
Original description
The description as published by the source.
Excessive caching of authentication context in Neo4j Enterprise edition versions prior to 2026.1.4 leads to authenticated users inheriting the context of the first user who authenticated after restart. The issue is limited to certain non-default configurations of SSO (UserInfo endpoint).
We recommend upgrading to versions 2026.1.4 (or 5.26.22) where the issue is fixed.
Source: NIST National Vulnerability Database NVD
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-1471 has been found in neo4j.
Risk of unauthorized operations or information disclosure.
What to do: upgrade neo4j to 5.26.22, 2026.1.4 or later.
If unsure, ask your IT team or search "neo4j CVE-2026-1471" on the vendor's site.
CVE-2026-1471 (neo4j) — CWE-863
Patched: 5.26.22, 2026.1.4 — 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: ?. Risk of unauthorized operations or information disclosure.
Update to 5.26.22, 2026.1.4.
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.1.4ステージング環境で 5.26.22, 2026.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory neo4j.com
- web nvd.nist.gov