Neo4j vulnerabilities: known CVEs & security history
Neo4j · Database · 5 tracked CVEs · 0 actively exploited · updated September 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Neo4j release lines — 5 in total. A CVE here doesn't mean your version is affected — check Neo4j's current status and the safe version to run.
Known Neo4j CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-1524 | critical | 9.8 | 0% | 2026 |
| CVE-2026-14587 | high | 7.5 | 0% | 2026 |
| CVE-2026-1497 | high | 7.2 | 0% | 2026 |
| CVE-2024-34517 | medium | 6.5 | 1% | 2024 |
| CVE-2026-1337 | medium | 5.4 | 0% | 2026 |
Is my Neo4j version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Neo4j version → · Monitor Neo4j for new CVEs →
Neo4j vulnerabilities — frequently asked
How many known vulnerabilities does Neo4j have?
IsItPatched tracks 5 CVEs for Neo4j. 1 is critical-severity and 2 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Neo4j have any actively-exploited vulnerabilities?
None of Neo4j's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Neo4j vulnerability?
Among tracked issues, CVE-2026-1524 (CRITICAL, CVSS 9.8) ranks highest — a Improper authentication weakness.
Is Neo4j safe to use?
It depends on the version. The latest supported Neo4j release (2026.07.1) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Neo4j security status · Neo4j end-of-life · actively-exploited CVEs. Always verify against Neo4j's advisories — see our disclaimer.