Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-4j3g-rwwq-4p54

Neo4j Enterprise and Community vulnerable to a potential information disclosure

CVSS 4.8 MediumEPSS 0.0016 · 5th percentile

Published by the GitHub Advisory Database at 4 Feb 2026, 12:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.neo4j:neo4jMaven<5.26.21 || >=2025.01.0, <2026.01.35.26.21, 2026.01.3
Identifiers
GHSA-4j3g-rwwq-4p54 · CVE-2026-1622
Weakness (CWE)
CWE-532
Tags
Published
4 Feb 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Neo4j Enterprise and Community, versions before 5.26.21 and from 2025.01.0 before 2026.01.3, can leak unredacted data into query logs. When the obfuscate_literals option is enabled, error messages are not redacted, so a user with access to the local log files, or who can run queries that trigger errors, may see information they are not authorised to view. Upgrade to 5.26.21 or 2026.01.3. After upgrading, enable db.logs.query.obfuscate_errors to also redact error messages, and restrict access to query log files.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.8 Medium 4.0 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 (Neo4j)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.