Neo4j 2026.09 · Version Status

Neo4j 2026.09 End of Life Date

Neo4j 2026.09 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

Neo4j 2026.09 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
2026.09.0
Standard release
Release Date
Sep 21, 2026
Neo4j 2026.09 series
Lifecycle detail

Neo4j 2026.09 was released on September 21, 2026 and has no published end-of-life date yet. It is not an LTS release; Neo4j reserves longer patch windows for its LTS versions. Its most recent patch is 2026.09.0, published September 16, 2026.

← Neo4j 2026.08 All Neo4j versions
20 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
20/30 High tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Neo4j Versions
VersionLatestEOL DateStatus
1.0 1.0.0 Aug 23, 2011 EOL
1.1 1.1.0 Jan 30, 2012 EOL
1.2 1.2.0 Jun 29, 2012 EOL
1.3 1.3.0 Sep 12, 2012 EOL
1.4 1.4.2 Jan 8, 2013 EOL
1.5 1.5.3 Mar 9, 2013 EOL
1.6 1.6.3 Jul 22, 2013 EOL
1.7 1.7.2 Oct 18, 2013 EOL

What does Neo4j 2026.09 end of life mean?

When Neo4j 2026.09 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Neo4j 2026.09 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Neo4j 2026.09 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Neo4j 2026.09 reach end of life?
Neo4j 2026.09 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is Neo4j 2026.09 still supported?
Yes, Neo4j 2026.09 is currently supported. The EOL date is TBD.
What should I upgrade to from Neo4j 2026.09?
The recommended upgrade from Neo4j 2026.09 is Neo4j 2026.09 — the latest actively supported version. Check the Neo4j full timeline for all supported versions.
What are the security risks of running Neo4j 2026.09 past EOL?
When Neo4j 2026.09 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Neo4j should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →