Advisory record · GHSA-4mpj-488r-vh6m

Neo4j Graph Database vulnerable to Path Traversal

CVSS 9.1 CriticalCriticalEPSS 0.015 · 75th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 1 Feb 2022, 22:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.neo4j.procedure:apocMaven<3.5.17 || >=4.2.0, <4.2.10 || >=4.3.0.0, <4.3.0.4 || >=4.4.0.0, <4.4.0.13.5.17, 4.2.10, 4.3.0.4, 4.4.0.1
Identifiers
GHSA-4mpj-488r-vh6m · CVE-2021-42767
Weakness (CWE)
CWE-22
Published
1 Feb 2022
Updated
8 Jul 2026

Machine-written summary

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

Neo4j APOC plugin (Maven org.neo4j.procedure:apoc) versions below 3.5.17, 4.2.0 through 4.2.9, 4.3.0.0 through 4.3.0.3, and 4.4.0.0 before 4.4.0.1 contain directory traversal flaws in several functions. An attacker who can call those functions can read and download files outside the configured directory, and in some cases create files. Upgrade to 3.5.17, 4.2.10, 4.3.0.4, or 4.4.0.1, or to the patched bundled version for your Neo4j release. If you cannot upgrade, restrict which procedures can run using the procedure allowlist setting.

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
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.015, the 75th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 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.