CVE-2024-34517: Neo4j · Cypher Component
Affects neo4jSource GCVE Database
Not known to be exploited : upgrade to 5.20.0 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.20.0
Exploitation evidence
Disclosed: evidence found.
CVE published 12 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade neo4j to 5.20.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamineo4jpkg:bitnami/neo4jOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available to remediate this vulnerability. Users should upgrade Neo4j to version 5.20.0 or later where the issue is fixed. Since this is not a cloud service, administrators must apply the update manually. No additional mitigation steps are indicated by the vendor advisory.
Description
Neo4j versions 5.0.0 through 5.18 contain a vulnerability in the Cypher component where IMMUTABLE privileges are mishandled in certain situations involving attackers with existing admin access. This flaw affects privilege handling but requires the attacker to already have administrative rights. A patch is available to address this issue.