CVE-2026-1524 Affecting neo4j-4.4-docker-publish package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-NEO4J44DOCKERPUBLISH-17093213
- published30 May 2026
- disclosed11 Mar 2026
Introduced: 11 Mar 2026
CVE-2026-1524 (opens in a new tab)How to fix?
There is no fixed version for Minimos:latest neo4j-4.4-docker-publish.
NVD Description
Note: Versions mentioned in the description apply only to the upstream neo4j-4.4-docker-publish package and not the neo4j-4.4-docker-publish package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
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.