CVE-2026-1622 Unredacted data exposure in query.log

What is CVE-2026-1622?

CVE-2026-1622 is a medium-severity vulnerability in neo4j Community Edition, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-532

Which versions are affected by CVE-2026-1622?

4 open source packages ship an affected version, including org.neo4j:neo4j.

How do I fix CVE-2026-1622?

Upgrade org.neo4j:neo4j to a fixed version for your release line: 5.26.21 or 2026.01.3.

Is CVE-2026-1622 being exploited?

There is no known exploitation of CVE-2026-1622 in the wild and no public exploit code.

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-4j3g-rwwq-4p54, MINI-2hv2-2qhm-vf6p, MINI-62w5-7c8q-wr46, MINI-873j-93vh-fhhr, MINI-8q73-qxjg-jmmv, MINI-925g-vcpm-4f87 and 5 more.