CVE-2026-1622

Unredacted data exposure in query.log

MEDIUM
4.8
CVSS Score
Published: February 4, 2026 at 09:14 AM UTC
Updated: June 17, 2026 at 10:16 AM UTC
1 product affected across 1 vendorNeo4j

Using Enterprise Edition by neo4j?

Get instant alerts when new vulnerabilities affect Enterprise Edition - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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_literal 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2025.01 ≤ v < 2026.01.34.4 ≤ v < 4.4.485.0 ≤ v < 5.26.212025.014.45.0
Affected range stops below 2026.01.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.4.48, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.26.21, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://neo4j.com/security/CVE-2026-1622

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.8MEDIUMNeo4j
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-532

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card