CVE-2026-1622 Affecting neo4j-4.4 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

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-15231469
  • published6 Feb 2026
  • disclosed4 Feb 2026

Introduced: 4 Feb 2026

CVE-2026-1622  (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.

Neo4j Enterprise and Community editions versions prior to 2026.01.3 and 5.26.21 are vulnerable to a potential information disclosure by a user who has ability to access the local log files.

The "obfuscate_literals" option in the query logs does not redact error information, exposing unredacted data in the query log when a customer writes a query that fails. It can allow a user with legitimate access to the local log files to obtain information they are not authorised to see. If this user is also in a position to run queries and trigger errors, this vulnerability can potentially help them to infer information they are not authorised to see through their intended database access.

We recommend upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had db.logs.query.obfuscate_literals enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting db.logs.query.obfuscate_errors once you have upgraded Neo4j.

CVSS Base Scores

version 3.1