CVE-2026-1524: Auth misconfiguration when multiple providers enabled
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-1524?
CVE-2026-1524 has a high severity level due to potential unauthorized access resulting from authentication misconfiguration.
How do I fix CVE-2026-1524?
To fix CVE-2026-1524, ensure proper configuration of OIDC providers by limiting simultaneous active providers as per the best practices outlined in the documentation.
What software versions are affected by CVE-2026-1524?
CVE-2026-1524 affects Neo4j Enterprise Edition versions prior to 2026.02.
What kind of vulnerability is CVE-2026-1524?
CVE-2026-1524 is an authentication misconfiguration vulnerability related to single sign-on (SSO) implementations.
Can CVE-2026-1524 be exploited remotely?
Yes, CVE-2026-1524 can be exploited remotely if the misconfiguration allows unauthorized access without proper authentication.