CVE-2026-1622: Neo4j Enterprise and Community vulnerable to a potential information disclosure

CVE-2026-1622 · Severity: medium · CVSS 4 · Published 2026-02-04

Neo4j Enterprise and Community vulnerable to a potential information disclosure

Technologies: org.neo4j:neo4j (Maven). Vendors: Maven.

Quick answers

Is CVE-2026-1622 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-1622 being exploited in the wild.
How severe is CVE-2026-1622?
Medium severity, with a CVSS score of 4, published 4 February 2026.
Which products and versions are affected?
org.neo4j:neo4j (Maven) ECOSYSTEM:introduced=0,fixed=5.26.21.
Is there a fix for CVE-2026-1622?
Yes. org.neo4j:neo4j (Maven): upgrade to 5.26.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-1622?
Check whether you run org.neo4j:neo4j (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.neo4j:neo4j (Maven): upgrade to 5.26.21 or later
    # set org.neo4j:neo4j to 5.26.21 in your pom.xml or build.gradle

Affected products

  • org.neo4j:neo4j (Maven) ECOSYSTEM:introduced=0,fixed=5.26.21

Identifiers

  • CVE-2026-1622
  • GHSA-4j3g-rwwq-4p54

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.