Neo4j · Lifecycle Status
Neo4j End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Neo4j versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
📅 Get reminded before Neo4j 5.26 reaches EOL on June 6, 2028 — alerts 90, 30 & 7 days out.
Latest Active
2026.05.0
2026.05 series
Next EOL
5.26
Jun 6, 2028
Active Versions
2
of 68 total
EOL Versions
66
no longer patched
Medium Risk
EOL Risk Score™ How is this calculated? →
EOL Recency
25/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 →
Release Cycle Timeline
■ EOL
■ Warning
■ Active
┊ Today
All Versions
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.0 | Feb 23, 2010 | Aug 23, 2011 | 5438 days past EOL | EOL |
| 1.1 | 1.1.0 | Jul 30, 2010 | Jan 30, 2012 | 5278 days past EOL | EOL |
| 1.2 | 1.2.0 | Dec 29, 2010 | Jun 29, 2012 | 5127 days past EOL | EOL |
| 1.3 | 1.3.0 | Apr 12, 2011 | Sep 12, 2012 | 5052 days past EOL | EOL |
| 1.4 | 1.4.2 | Jul 8, 2011 | Jan 8, 2013 | 4934 days past EOL | EOL |
| 1.5 | 1.5.3 | Nov 9, 2011 | Mar 9, 2013 | 4874 days past EOL | EOL |
| 1.6 | 1.6.3 | Jan 22, 2012 | Jul 22, 2013 | 4739 days past EOL | EOL |
| 1.7 | 1.7.2 | Apr 18, 2012 | Oct 18, 2013 | 4651 days past EOL | EOL |
| 1.8 | 1.8.3 | Sep 28, 2012 | Mar 28, 2014 | 4490 days past EOL | EOL |
| 1.9 | 1.9.9 | May 21, 2013 | Nov 21, 2014 | 4252 days past EOL | EOL |
| 2.0 | 2.0.5 | Dec 11, 2013 | Jun 11, 2015 | 4050 days past EOL | EOL |
| 2.1 | 2.1.8 | May 29, 2014 | Nov 29, 2015 | 3879 days past EOL | EOL |
| 2.2 | 2.2.10 | Mar 25, 2015 | Sep 25, 2016 | 3578 days past EOL | EOL |
| 2.3 | 2.3.12 | Oct 21, 2015 | Apr 21, 2017 | 3370 days past EOL | EOL |
| 3.0 | 3.0.12 | Apr 16, 2016 | Oct 31, 2017 | 3177 days past EOL | EOL |
| 3.1 | 3.1.9 | Dec 13, 2016 | Jun 13, 2018 | 2952 days past EOL | EOL |
| 3.2 | 3.2.14 | May 11, 2017 | Nov 30, 2018 | 2782 days past EOL | EOL |
| 3.3 | 3.3.9 | Oct 24, 2017 | Apr 28, 2019 | 2633 days past EOL | EOL |
| 3.4 | 3.4.18 | May 17, 2018 | Mar 31, 2020 | 2295 days past EOL | EOL |
| 3.5 | 3.5.35 | Nov 29, 2018 | May 27, 2022 | 1508 days past EOL | EOL |
| 4.0 | 4.0.12 | Jan 15, 2020 | Jul 14, 2021 | 1825 days past EOL | EOL |
| 4.1 | 4.1.12 | Jun 23, 2020 | Dec 22, 2021 | 1664 days past EOL | EOL |
| 4.2 | 4.2.19 | Nov 17, 2020 | May 16, 2022 | 1519 days past EOL | EOL |
| 4.3 | 4.3.23 | Jun 17, 2021 | Dec 16, 2022 | 1305 days past EOL | EOL |
| 4.4 LTS | 4.4.48 | Dec 2, 2021 | Nov 30, 2025 | 225 days past EOL | EOL |
| 5.1 | 5.1.0 | Oct 24, 2022 | Nov 21, 2022 | 1330 days past EOL | EOL |
| 5.2 | 5.2.0 | Nov 21, 2022 | Dec 15, 2022 | 1306 days past EOL | EOL |
| 5.3 | 5.3.0 | Dec 15, 2022 | Jan 26, 2023 | 1264 days past EOL | EOL |
| 5.4 | 5.4.0 | Jan 26, 2023 | Feb 16, 2023 | 1243 days past EOL | EOL |
| 5.5 | 5.5.0 | Feb 16, 2023 | Mar 24, 2023 | 1207 days past EOL | EOL |
| 5.6 | 5.6.0 | Mar 24, 2023 | Apr 20, 2023 | 1180 days past EOL | EOL |
| 5.7 | 5.7.0 | Apr 20, 2023 | May 16, 2023 | 1154 days past EOL | EOL |
| 5.8 | 5.8.0 | May 16, 2023 | Jun 15, 2023 | 1124 days past EOL | EOL |
| 5.9 | 5.9.0 | Jun 15, 2023 | Jul 19, 2023 | 1090 days past EOL | EOL |
| 5.10 | 5.10.0 | Jul 19, 2023 | Aug 15, 2023 | 1063 days past EOL | EOL |
| 5.11 | 5.11.0 | Aug 14, 2023 | Sep 14, 2023 | 1033 days past EOL | EOL |
| 5.12 | 5.12.0 | Sep 15, 2023 | Oct 23, 2023 | 994 days past EOL | EOL |
| 5.13 | 5.13.0 | Oct 23, 2023 | Nov 24, 2023 | 962 days past EOL | EOL |
| 5.14 | 5.14.0 | Nov 24, 2023 | Dec 15, 2023 | 941 days past EOL | EOL |
| 5.15 | 5.15.0 | Dec 15, 2023 | Jan 22, 2024 | 903 days past EOL | EOL |
| 5.16 | 5.16.0 | Jan 22, 2024 | Feb 23, 2024 | 871 days past EOL | EOL |
| 5.17 | 5.17.0 | Feb 23, 2024 | Mar 13, 2024 | 852 days past EOL | EOL |
| 5.18 | 5.18.1 | Mar 13, 2024 | Apr 12, 2024 | 822 days past EOL | EOL |
| 5.19 | 5.19.0 | Apr 12, 2024 | May 23, 2024 | 781 days past EOL | EOL |
| 5.20 | 5.20.0 | May 23, 2024 | Jun 28, 2024 | 745 days past EOL | EOL |
| 5.21 | 5.21.2 | Jun 28, 2024 | Jul 24, 2024 | 719 days past EOL | EOL |
| 5.22 | 5.22.0 | Jul 24, 2024 | Aug 22, 2024 | 690 days past EOL | EOL |
| 5.23 | 5.23.0 | Aug 22, 2024 | Sep 27, 2024 | 654 days past EOL | EOL |
| 5.24 | 5.24.2 | Sep 27, 2024 | Oct 31, 2024 | 620 days past EOL | EOL |
| 5.25 | 5.25.1 | Oct 31, 2024 | Dec 6, 2024 | 584 days past EOL | EOL |
| 5.26 LTS | 5.26.28 | Dec 6, 2024 | Jun 6, 2028 | 694 days remaining | Active |
| 2025.01 | 2025.01.0 | Feb 6, 2025 | Feb 27, 2025 | 501 days past EOL | EOL |
| 2025.02 | 2025.02.0 | Feb 27, 2025 | Mar 27, 2025 | 473 days past EOL | EOL |
| 2025.03 | 2025.03.0 | Mar 27, 2025 | Apr 30, 2025 | 439 days past EOL | EOL |
| 2025.04 | 2025.04.0 | Apr 30, 2025 | Jun 3, 2025 | 405 days past EOL | EOL |
| 2025.05 | 2025.05.1 | Jun 3, 2025 | Jul 2, 2025 | 376 days past EOL | EOL |
| 2025.06 | 2025.06.2 | Jul 2, 2025 | Jul 31, 2025 | 347 days past EOL | EOL |
| 2025.07 | 2025.07.1 | Jul 31, 2025 | Aug 15, 2025 | 332 days past EOL | EOL |
| 2025.08 | 2025.08.0 | Aug 27, 2025 | Sep 29, 2025 | 287 days past EOL | EOL |
| 2025.09 | 2025.09.0 | Sep 29, 2025 | Oct 30, 2025 | 256 days past EOL | EOL |
| 2025.10 | 2025.10.1 | Oct 30, 2025 | Dec 19, 2025 | 206 days past EOL | EOL |
| 2025.11 | 2025.11.2 | Dec 19, 2025 | Jan 16, 2026 | 178 days past EOL | EOL |
| 2025.12 | 2025.12.1 | Jan 16, 2026 | Feb 3, 2026 | 160 days past EOL | EOL |
| 2026.01 | 2026.01.4 | Feb 10, 2026 | Mar 6, 2026 | 129 days past EOL | EOL |
| 2026.02 | 2026.02.3 | Mar 20, 2026 | Apr 2, 2026 | 102 days past EOL | EOL |
| 2026.03 | 2026.03.1 | Apr 2, 2026 | Apr 23, 2026 | 81 days past EOL | EOL |
| 2026.04 | 2026.04.0 | Apr 23, 2026 | May 28, 2026 | 46 days past EOL | EOL |
| 2026.05 | 2026.05.0 | May 28, 2026 | TBD | Supported | Active |
What does Neo4j end of life mean for your organization?
When a version of Neo4j reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Neo4j should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Neo4j versions. This is a bridge, not a permanent solution — plan your migration in parallel.
endoflife.ai
Get Neo4j Support Options
Neo4j has 66 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.
Get My Support Options →Frequently Asked Questions
What is the end-of-life date for Neo4j?
The next Neo4j version reaching EOL is 5.26 on June 6, 2028. See the full table above for all version EOL dates.
When is the Neo4j support end date?
The next Neo4j support end date is June 6, 2028, when version 5.26 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Neo4j?
The latest active version of Neo4j is 2026.05.0. Always verify against the table above as support windows can change.
What happens when Neo4j reaches end of life?
When Neo4j reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Neo4j?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Neo4j versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.