neo4j Enterprise Edition up to 5.26.21/2026.1 SSO authorization

Summaryinfo

A vulnerability was found in neo4j Enterprise Edition up to 5.26.21/2026.1. It has been declared as problematic. This affects an unknown function of the component SSO. Such manipulation leads to authorization. This vulnerability is listed as CVE-2026-1524. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in neo4j Enterprise Edition up to 5.26.21/2026.1. It has been rated as problematic. Affected by this issue is some unknown processing of the component SSO. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at neo4j.com. This vulnerability is handled as CVE-2026-1524 since 01/28/2026. The exploitation is known to be easy. The attack may be launched remotely. Additional levels of successful authentication are necessary for exploitation. There are neither technical details nor an exploit publicly available.

Upgrading to version 5.26.22 or 2026.02 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• neo4j

Name

• Enterprise Edition

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.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion