PublishedCVE-2026-1497·
2.0Low
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2026.02 and 5.26.22.
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.
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| neo4j | >=2025.01 <2026.02, >=5.0 <5.26.22 | 2026.02, 5.26.22 |
Every event on this vulnerability
A live severity badge for an advisory, README or ticket