Information
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.
For Enterprise and Community customers:
Applicability
Only applicable if
db.logs.query.obfuscate_literals is enabled
Solution
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.
For Aura customers:
If you are not using the Query Log Forwarding feature and have not downloaded Query Logs from Aura in the past, no action is required. Otherwise, you may want to review the access logs and permissions for the query logging data downloaded from Aura. You can optionally redact or remove the downloaded log files as a precautionary measure.
Links
