How severe is CVE-2022-37423?

No CVSS score has been assigned to CVE-2022-37423 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-37423?

CVE-2022-37423 affects the following packages: org.neo4j.procedure:apoc (Maven), org.neo4j.procedure:apoc (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-37423?

Update org.neo4j.procedure:apoc to 4.4.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37423 is resolved across your whole dependency graph.

How do I detect CVE-2022-37423 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.neo4j.procedure:apoc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-37423 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2022-37423 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-37423, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-37423?

CVE-2022-37423 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-37423?

CVE-2022-37423 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-37423 published, and has it been updated?

CVE-2022-37423 was published on August 12, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2022-37423 — apoc

Fix: neo4j-contrib/neo4j-apoc-procedures#3080

CVE-2022-37423 is a Path Traversal vulnerability in org.neo4j.procedure:apoc. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.neo4j.procedure:apoc — see the affected versions and patch details below.

Neo4j Graph apoc plugins Partial Path Traversal Vulnerability

Also known asGHSA-78f9-745f-278p

Published

Aug 12, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk+0.07%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.neo4j.procedure:apoc☕org.neo4j.procedure:apoc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A partial Directory Traversal Vulnerability found in apoc.log.stream function of apoc plugins in Neo4j Graph database. This issue allows a malicious actor to potentially break out of the expected directory. The impact is limited to sibling directories. For example, userControlled.getCanonicalPath().startsWith("/usr/out") will allow an attacker to access a directory with a name like /usr/outnot.

Patches

The users should aim to use the latest released version compatible with their Neo4j version. The minimum versions containing patch for this vulnerability are 4.4.0.8 and 4.3.0.7

Workarounds

If you cannot upgrade the library, you can control the allowlist of the functions that can be used in your system

For more information

If you have any questions or comments about this advisory:

Open an issue in neo4j-apoc-procedures
Email us at [email protected]

Credits

We want to publicly recognise the contribution of Jonathan Leitschuh for reporting this issue.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.neo4j.procedure:apoc`	≥ 4.4.0.0&&< 4.4.0.8	4.4.0.8`org.neo4j.procedure:apoc:4.4.0.8`
☕Maven	`org.neo4j.procedure:apoc`	all versions	4.3.0.7`org.neo4j.procedure:apoc:4.3.0.7`

Affected Products

1 product · 2 configurations

Application

awesome procedures on cypherneo4j

≥ 4.4.0.0 && < 4.4.0.8

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Neo4j APOC (Awesome Procedures on Cypher) before 4.3.0.7 and 4.x before …

github.comNVDAug 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.neo4j.procedure:apoc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.neo4j.procedure:apoc to 4.4.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37423 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Impact A partial Directory Traversal Vulnerability found in `apoc.log.stream` function of apoc plugins in Neo4j Graph database. This issue allows a malicious actor to potentially break out of the expected directory. The impact is limited to sibling directories. For example, `userControlled.getCanonicalPath().startsWith("/usr/out")` will allow an attacker to access a directory with a name like `/usr/outnot`. ### Patches The users should aim to use the latest released version compatible with their Neo4j version. The minimum versions containing patch for this vulnerability are 4.4.0.8 and 4

O3 Security · Impact-Aware SCA

Is CVE-2022-37423 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works