CVE-2026-1622 Details
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_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.
A vulnerability allowing information disclosure exists in Neo4j Enterprise and Community editions prior to versions 2026.01.3 and 5.26.21. The issue arises because the 'obfuscate_literals' option in query logs does not properly redact error information. This oversight can expose unredacted data when a query fails, potentially allowing users with access to local log files to see unauthorized information. If such a user can also execute queries that trigger errors, they might infer additional sensitive data through their database access.
Users are advised to upgrade to Neo4j versions 2026.01.3 or 5.26.21, where this issue has been fixed. After upgrading, review the permissions on query log files to ensure restricted access. If 'db.logs.query.obfuscate_literals' was enabled and the obfuscation needs to cover error messages as well, the new setting 'db.logs.query.obfuscate_errors' should be enabled post-upgrade.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Feb 4, 2026CISA-ADP
Assessed Feb 4, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://neo4j.com/security/CVE-2026-1622 | Neo4j | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-532 | Insertion of Sensitive Information into Log File | Neo4j |
Affected Products
| Product | Versions |
|---|---|
| Neo4j | < 2026.01.3 (semver) < 5.26.21 (semver) |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | Neo4j |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 4, 2026 | CVE Modified | Neo4j |
| Feb 4, 2026 | New CVE Received | Neo4j |
Volerion