CVE-2026-1471
Received Received - Intake
Authentication Context Caching Flaw in Neo4j Enterprise Enables Privilege Inheritance

Publication date: 2026-03-11

Last updated on: 2026-03-11

Assigner: Neo4j

Description
Excessive caching of authentication context in Neo4j Enterprise edition versions prior to 2026.01.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.01.4 (or 5.26.22) where the issue is fixed.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-11
Last Modified
2026-03-11
Generated
2026-05-07
AI Q&A
2026-03-11
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
neo4j enterprise to 2026.01.4 (exc)
neo4j enterprise 5.26.22
neo4j neo4j_enterprise to 2026.01.4 (exc)
neo4j neo4j_enterprise to 5.26.22 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :

This vulnerability can lead to unauthorized access by allowing users to assume the identity or privileges of another authenticated user due to improper handling of authentication context.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


Can you explain this vulnerability to me?

CVE-2026-1471 is a security vulnerability in Neo4j Enterprise edition versions prior to 2026.01.4. It involves excessive caching of the authentication context, which causes authenticated users to inherit the authentication context of the first user who logged in after a server restart.

This issue specifically affects certain non-default configurations of Single Sign-On (SSO) that use the UserInfo endpoint.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, it is recommended to upgrade Neo4j Enterprise edition to version 2026.01.4 (or 5.26.22) where the issue has been fixed.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart