Neo4j Enterprise and Community vulnerable to a potential information disclosure

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-1622: 0.16% estimated exploitation activity in the next 30 days; percentile 5.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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,…

Published by the source

4 Feb 2026, 12:31 UTC

Last modified by the source

4 Feb 2026, 20:28 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4j3g-rwwq-4p54

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-1622

Advisory: Neo4j Enterprise and Community vulnerable to a potential information disclosure
IDs: CVE-2026-1622, GHSA-4j3g-rwwq-4p54
Record: https://patchnext.com/advisories/cve-2026-1622 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.neo4j:neo4j 2026.01.3, 5.26.21. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.neo4j:neo4j: affected < 5.26.21; >= 2025.01.0, < 2026.01.3; fixed in 5.26.21, 2026.01.3

## Suggested inspection (read-only)
- Maven org.neo4j:neo4j: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.neo4j:neo4j.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4j3g-rwwq-4p54 (GitHub-reviewed advisory GHSA-4j3g-rwwq-4p54 lists affected ranges: Maven org.neo4j:neo4j >=0 =2025.01.0 <2026.01.3)

Commands are suggestions: review each one before running it.