CVE-2026-1497

HighCVSS 7.2

Published: 11/03/2026(UTC)Updated: 28/08/2026(UTC)Translated: 15/06/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.24%

14th percentile - higher than 14% of all known CVEs

Summary

In Neo4j Enterprise versions prior to 2026.02 and 5.26.22, there is a bug in resolving namespaces in composite databases. Administrators may inadvertently grant access to local databases or remote aliases named 'name', leading to unintended privileges.

Risk Assessment

Organizations may be exposed to unauthorized data access, potentially leading to information leaks or privacy violations. The risk increases when new databases or aliases are created after privileges are granted.

Recommendation

It is recommended to upgrade to the latest version of Neo4j Enterprise to mitigate this vulnerability. Additionally, administrators should carefully review granted permissions and avoid using generic namespace names.

Other vulnerabilities in Neo4j Enterprise

CVE-2026-1524Critical
In Neo4j Enterprise versions prior to 2026.02, there is an issue with SSO implementation that can lead to unauthorized access. This occurs when an admin configures multiple OIDC providers, some of which are authentication-only but may also provide authorization.

Original NVD description (English 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.