CVE-2026-1622: Neo4j Neo4j Enterprise And Community Vulnerable Vulnerability

MODERATE
Advisory Identifier: GHSA-4j3g-rwwq-4p54
Share
CWE-532
Published
Advisory Summary

CVE-2026-1622 is a MODERATE neo4j enterprise and community vulnerable vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Neo4j libraries in the Maven ecosystem. The issue involves neo4j enterprise and community vulnerable to a potential information disclosure. Remediation is available by upgrading affected packages to version 5.26.21, 2026.01.3.

CVE-2026-1622 at a Glance

CVE Identifier CVE-2026-1622
GHSA Identifier GHSA-4j3g-rwwq-4p54
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Neo4j
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-1622

To remediate this vulnerability, upgrade all affected Neo4j dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.neo4j:neo4j fixed: 5.26.21 
<dependency>
    <groupId>org.neo4j</groupId>
    <artifactId>neo4j</artifactId>
    <version>5.26.21</version>
</dependency>
org.neo4j:neo4j fixed: 2026.01.3 
<dependency>
    <groupId>org.neo4j</groupId>
    <artifactId>neo4j</artifactId>
    <version>2026.01.3</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=org.neo4j

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-1622, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.neo4j

Analyze the terminal output to locate any version of Neo4j in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.26.21), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.neo4j command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In Neo4j, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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. 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.obfuscate_literals enabled, and users wish for the obfuscation to cover the error messages as well, theyneed to enable the new configuration setting db.logs.query.obfuscate_errors once they have upgraded Neo4j.

CVE-2026-1622 Affected Neo4j Versions

2 component(s)
Fixed Versions:
5.26.212026.01.3
Product / Package Ecosystem Affected Versions Fixed Version
org.neo4j:neo4j
maven/org.neo4j/neo4j
Maven
< 5.26.21
5.26.21
org.neo4j:neo4j
maven/org.neo4j/neo4j
Maven
≥ 2025.01.0
< 2026.01.3
2026.01.3

References

NVD — CVE-2026-1622 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-1622
Neo4j Source Repository REPOSITORY
https://github.com/neo4j/neo4j
Neo4j Security Information SECURITY
https://neo4j.com/security/CVE-2026-1622

Frequently Asked Questions

What is CVE-2026-1622?
CVE-2026-1622 is a security vulnerability in Neo4j involving Neo4j Enterprise and Community vulnerable to a potential information disclosure under CWE-532: Insertion of Sensitive Information into Log File.
Which Neo4j versions are affected?
Affected versions include releases prior to 5.26.21, 2026.01.3 across affected packages: org.neo4j:neo4j.
What version fixes CVE-2026-1622?
Upgrading to 5.26.21, 2026.01.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is neo4j affected?
Yes, org.neo4j:neo4j is affected in releases prior to 5.26.21, 2026.01.3. Upgrade your dependency to 5.26.21, 2026.01.3 or later.
What CWE is associated with CVE-2026-1622?
CVE-2026-1622 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check Maven dependencies for CVE-2026-1622?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.neo4j'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4j3g-rwwq-4p54",
  "modified" : "2026-02-04T20:28:55Z",
  "published" : "2026-02-04T12:31:25Z",
  "aliases" : [ "CVE-2026-1622" ],
  "summary" : "Neo4j Enterprise and Community vulnerable to a potential information disclosure",
  "details" : "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.\n\nThe \"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.\n\nNeo4j 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.obfuscate_literals enabled, and users wish for the obfuscation to cover the error messages as well, theyneed to enable the new configuration setting db.logs.query.obfuscate_errors once they have upgraded Neo4j.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.neo4j:neo4j"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.26.21"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.neo4j:neo4j"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2025.01.0"
      }, {
        "fixed" : "2026.01.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-1622"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/neo4j/neo4j"
  }, {
    "type" : "WEB",
    "url" : "https://neo4j.com/security/CVE-2026-1622"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-04T20:28:55Z",
    "nvd_published_at" : "2026-02-04T10:16:04Z"
  }
}