CVE-2026-1497
Received Received - Intake
Namespace Resolution Flaw in Neo4j Enterprise Enables Unauthorized Access

Publication date: 2026-03-11

Last updated on: 2026-03-11

Assigner: Neo4j

Description
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.
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 2 associated CPEs
Vendor Product Version / Range
neo4j enterprise to 2026.02 (exc)
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
Can you explain this vulnerability to me?

This vulnerability involves incorrect resolving of namespaces in composite databases in Neo4j Enterprise edition prior to versions 2026.02 and 5.26.22. Specifically, when an administrator tries to grant a user access to a remote database constituent named "namespace.name", the system may mistakenly grant access to any local database or remote alias simply called "name". Furthermore, if such a database or alias does not exist at the time the command is run, the privileges will still apply if it is created later.


How can this vulnerability impact me? :

The impact of this vulnerability is that users may receive unintended access privileges to local databases or remote aliases that they should not have access to. This could lead to unauthorized access to data or resources within the Neo4j Enterprise environment, potentially exposing sensitive information or allowing actions beyond the intended scope of access.


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

I don't know


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

I don't know


What immediate steps should I take to mitigate this vulnerability?

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