01 Record
CVE-2026-1622
Unredacted data exposure in query.log
MediumPUBLISHEDCNA: Neo4j
CNA base score4.8 CVSS v4.0CVSS: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
02 Description
Unredacted data exposure in query.log
03 Exploitation and scoring
- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
- EPSS probability
- 0.16% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 5.3% of scored records. A rank, not a probability.
- NVD base score
- 4.8 (CVSS v4.0), scored by the NVD independently of the CNA.
- NVD CVSS vector
- 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
- NVD analysis status
- Deferred. NVD last modified this record on 2026-06-17.
- Red Hat severity
- Moderate. Red Hat's rating for its own products, not a CVSS rating.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-02-04 09:14Z8 MO AGO
- Last updated
- 2026-02-04 15:12Z8 MO AGO
- Reserved
- 2026-01-29
- Assigning CNA
- Neo4j
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 4.8)
- CNA CVSS vector
- 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
- Weaknesses
- CWE-532Insertion of Sensitive Information into Log FileBase
- Data version
- 5.2
- Document digest
- e668faf1feac7fd907337244bb5e68c046d59d81b6d934f4e1b1bd9771d631e8
05 Affected products
VendorProductVersionsPlatforms
06 References
07 Remediation
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.