CVE-2026-1622 json
Unredacted data exposure in query.log
published 9mo ago modified last mo. also GHSA-4j3g-rwwq-4p54 , EUVD-2026-5512
- cvss
- 4.8
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.neo4j:neo4j 5.26.21, 2026.01.3
- neo4j Enterprise Edition 4.4.48, 5.26.21, 2026.01.3
- neo4j Community Edition 4.4.48, 5.26.21, 2026.01.3
Is CVE-2026-1622 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-1622 updated cvss 5.5
neo4j: Unredacted data exposure in query.log
-
Red Hat build of Apache Camel for Spring Boot 4 camel-neo4j, neo4j-java-driver, neo4j-bolt-connection, neo4j-bolt-connection-netty, neo4j-bolt-connection-pooled, neo4j-bolt-connection-routed Red Hat Fuse 7 neo4j-ogm-core Red Hat JBoss Enterprise Application Platform 8 neo4j Red Hat JBoss Enterprise Application Platform Expansion Pack neo4j Red Hat OpenShift AI (RHOAI) rhoai/odh-model-registry-rhel9 Red Hat OpenShift Container Platform 4 openshift4/oc-mirror-plugin-rhel9affected: workaround, no fix available “Fix deferred”
+1 more productsfewer
Red Hat OpenShift Dev Spaces devspaces/dashboard-rhel9, devspaces/devspaces-operator-bundle
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9mo ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 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/AU:N/R:U/V:D/RE:M |
| CNA | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:D/RE:M/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.neo4j:neo4j | <5.26.21 >=2025.01.0, <2026.01.3 |
5.26.21 2026.01.3 |
Affected products
- neo4j Enterprise Edition
- neo4j Community Edition
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
References
-
neo4j.com
/security/CVE-2026-1622
vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-1622
advisory
-
github.com
/neo4j/neo4j
package
Sources
- CVE List CVE-2026-1622
- GitHub Advisory GHSA-4j3g-rwwq-4p54
- NVD CVE-2026-1622
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.