Information Exposure Affecting neo4j-4.4 package, versions *


Severity

Recommended
0.0
low
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.01% (1st percentile)

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-NEO4J44-15266572
  • published12 Feb 2026
  • disclosed10 Feb 2026

Introduced: 10 Feb 2026

CVE-2026-23901  (opens in a new tab)
CWE-208  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest neo4j-4.4.

NVD Description

Note: Versions mentioned in the description apply only to the upstream neo4j-4.4 package and not the neo4j-4.4 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Observable Timing Discrepancy vulnerability in Apache Shiro.

This issue affects Apache Shiro: from 1., 2. before 2.0.7.

Users are recommended to upgrade to version 2.0.7 or later, which fixes the issue.

Prior to Shiro 2.0.7, code paths for non-existent vs. existing users are different enough, that a brute-force attack may be able to tell, by timing the requests only, determine if the request failed because of a non-existent user vs. wrong password.

The most likely attack vector is a local attack only. Shiro security model  https://shiro.apache.org/security-model.html#username_enumeration  discusses this as well.

Typically, brute force attack can be mitigated at the infrastructure level.

CVSS Base Scores

version 3.1