CVE-2026-1622: Unredacted data exposure in query.log
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 "obfuscateliterals" 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.obfuscateliterals enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting db.logs.query.obfuscateerrors once you have upgraded Neo4j.
Other sources
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 "obfuscateliterals" 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.
Neo4j recommends 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 a project's configuration had db.logs.query.obfuscateliterals enabled, and users wish for the obfuscation to cover the error messages as well, theyneed to enable the new configuration setting db.logs.query.obfuscateerrors once they have upgraded Neo4j.
— GitHub
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2026-1622?
CVE-2026-1622 is rated as having a high severity due to the potential for information disclosure.
How do I fix CVE-2026-1622?
To fix CVE-2026-1622, upgrade to Neo4j Enterprise or Community editions version 2026.01.3 or 5.26.21 or later.
Who is affected by CVE-2026-1622?
CVE-2026-1622 affects users of Neo4j Enterprise and Community editions prior to versions 2026.01.3 and 5.26.21.
What type of vulnerability is CVE-2026-1622?
CVE-2026-1622 is classified as an information disclosure vulnerability.
What options in Neo4j are related to CVE-2026-1622?
CVE-2026-1622 is related to the 'obfuscate_literals' option in the query logs of Neo4j.