Skip to content

CVE-2026-1524

Neo4j authentication bypass

9.8 CRITICALEPSS 0.32%
  1. Published11 Mar 2026

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Neo4j≥ 2025.01.0 < 2026.02.0 · < 5.26.22

Remediation

Fixed in
Neo4j≥ 2026.02.0

Frequently asked

Is CVE-2026-1524 being actively exploited?

CVE-2026-1524 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.32%.

How severe is CVE-2026-1524?

CVE-2026-1524 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.32% probability of exploitation.

Which products are affected by CVE-2026-1524?

Affected products include Neo4j.

How do I fix CVE-2026-1524?

Upgrade affected software to a fixed version, for example Neo4j 2026.02.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-1524 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.