Neo4j Neo4j
CVE-2026-1497
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.
What this means for your business
- It affects Neo4j. It matters if your company, or a supplier that handles your data, runs it.
- An attacker can use it remotely, over a network, with an administrator login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 0.2% chance of attack attempts being seen in the next 30 days, ranking above 14% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Neo4j, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 7.2 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H- CVSS v4
- 2.0
- Weakness
- CWE-863
- Assigned by
- 3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6
Dates
- Published
- 2026-03-11
- Last modified
- 2026-08-28
- Sources
- NVD
Affected products
- Neo4j Neo4j- 5.26.22, 2025.01.0 - 2026.02.0
As listed in the NVD configuration data. Not a statement about your estate.