neo4j Enterprise Edition up to 5.26.21/2026.1 Composite Databases authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in neo4j Enterprise Edition up to 5.26.21/2026.1. The impacted element is an unknown function of the component Composite Databases. Performing a manipulation results in authorization. This vulnerability is known as CVE-2026-1497. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in neo4j Enterprise Edition up to 5.26.21/2026.1. This affects an unknown code of the component Composite Databases. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as 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. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at neo4j.com. This vulnerability is uniquely identified as CVE-2026-1497 since 01/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 5.26.22 or 2026.02 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 5.26.0
- 5.26.1
- 5.26.2
- 5.26.3
- 5.26.4
- 5.26.5
- 5.26.6
- 5.26.7
- 5.26.8
- 5.26.9
- 5.26.10
- 5.26.11
- 5.26.12
- 5.26.13
- 5.26.14
- 5.26.15
- 5.26.16
- 5.26.17
- 5.26.18
- 5.26.19
- 5.26.20
- 5.26.21
- 2026.0
- 2026.1
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Enterprise Edition 5.26.22/2026.02
Timeline
01/27/2026 CVE reserved03/11/2026 Advisory disclosed
03/11/2026 VulDB entry created
05/17/2026 VulDB entry last update
Sources
Advisory: neo4j.comStatus: Confirmed
CNA: Neo4j
CVE: CVE-2026-1497 (🔒)
GCVE (CVE): GCVE-0-2026-1497
GCVE (VulDB): GCVE-100-350445
Entry
Created: 03/11/2026 17:34Updated: 05/17/2026 03:55
Changes: 03/11/2026 17:34 (71), 03/14/2026 12:43 (1), 05/17/2026 03:55 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.