CVE-2026-1524 json
Auth misconfiguration when multiple providers enabled
published 2026-03-11 7 mo ago modified 2026-09-10 1 mo ago also BIT-neo4j-2026-1524 , BIT-neo4j-enterprise-2026-1524 , EUVD-2026-11212
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to unauthorised access under the following conditions:
If a neo4j admin configures two or more OIDC providers AND configures one or more of them to be an authorization provider AND configures one or more of them to be authentication-only, then those that are authentication-only will also provide authorization. This edgecase becomes a security problem only if the authentication-only provider contains groups which have higher privileges than provided by the intended (configured) authorization provider.
When using multiple plugins for authentication and authorisation, prior to the fix the issue could lead to a plugin configured to provide only authentication or authorisation capabilities erroneously providing both capabilities.
We recommend upgrading to versions 2026.02 (or 5.26.22) where the issue is fixed.
Patch / fix
- bitnami neo4j 5.26.22, 2026.2.0
- bitnami neo4j-enterprise 5.26.22, 2026.2.0
- neo4j Enterprise Edition 5.26.22, 2026.02
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/AU:N/R:U/V:D/RE:M/U:Green |
| CNA | 4.0 | 2.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:Green |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | neo4j | <5.26.22 >=2025.1.0, <2026.2.0 |
5.26.22 2026.2.0 |
| bitnami | neo4j-enterprise | <5.26.22 >=2025.1.0, <2026.2.0 |
5.26.22 2026.2.0 |
Affected products
- neo4j Enterprise Edition
Classification
References
-
neo4j.com
/security/CVE-2026-1524
vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-1524
web
Sources
- CVE List CVE-2026-1524
- NVD CVE-2026-1524
- OSV BIT-neo4j-2026-1524
- OSV BIT-neo4j-enterprise-2026-1524
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.