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.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.0 | Feb 23, 2010 | Aug 23, 2011 | 5465 days past EOL | EOL |
| 1.1 | 1.1.0 | Jul 30, 2010 | Jan 30, 2012 | 5305 days past EOL | EOL |
| 1.2 | 1.2.0 | Dec 29, 2010 | Jun 29, 2012 | 5154 days past EOL | EOL |
| 1.3 | 1.3.0 | Apr 12, 2011 | Sep 12, 2012 | 5079 days past EOL | EOL |
| 1.4 | 1.4.2 | Jul 8, 2011 | Jan 8, 2013 | 4961 days past EOL | EOL |
| 1.5 | 1.5.3 | Nov 9, 2011 | Mar 9, 2013 | 4901 days past EOL | EOL |
| 1.6 | 1.6.3 | Jan 22, 2012 | Jul 22, 2013 | 4766 days past EOL | EOL |
| 1.7 | 1.7.2 | Apr 18, 2012 | Oct 18, 2013 | 4678 days past EOL | EOL |
| 1.8 | 1.8.3 | Sep 28, 2012 | Mar 28, 2014 | 4517 days past EOL | EOL |
| 1.9 | 1.9.9 | May 21, 2013 | Nov 21, 2014 | 4279 days past EOL | EOL |
| 2.0 | 2.0.5 | Dec 11, 2013 | Jun 11, 2015 | 4077 days past EOL | EOL |
| 2.1 | 2.1.8 | May 29, 2014 | Nov 29, 2015 | 3906 days past EOL | EOL |
| 2.2 | 2.2.10 | Mar 25, 2015 | Sep 25, 2016 | 3605 days past EOL | EOL |
| 2.3 | 2.3.12 | Oct 21, 2015 | Apr 21, 2017 | 3397 days past EOL | EOL |
| 3.0 | 3.0.12 | Apr 16, 2016 | Oct 31, 2017 | 3204 days past EOL | EOL |
| 3.1 | 3.1.9 | Dec 13, 2016 | Jun 13, 2018 | 2979 days past EOL | EOL |
| 3.2 | 3.2.14 | May 11, 2017 | Nov 30, 2018 | 2809 days past EOL | EOL |
| 3.3 | 3.3.9 | Oct 24, 2017 | Apr 28, 2019 | 2660 days past EOL | EOL |
| 3.4 | 3.4.18 | May 17, 2018 | Mar 31, 2020 | 2322 days past EOL | EOL |
| 3.5 | 3.5.35 | Nov 29, 2018 | May 27, 2022 | 1535 days past EOL | EOL |
| 4.0 | 4.0.12 | Jan 15, 2020 | Jul 14, 2021 | 1852 days past EOL | EOL |
| 4.1 | 4.1.12 | Jun 23, 2020 | Dec 22, 2021 | 1691 days past EOL | EOL |
| 4.2 | 4.2.19 | Nov 17, 2020 | May 16, 2022 | 1546 days past EOL | EOL |
| 4.3 | 4.3.23 | Jun 17, 2021 | Dec 16, 2022 | 1332 days past EOL | EOL |
| 4.4 LTS | 4.4.48 | Dec 2, 2021 | Nov 30, 2025 | 252 days past EOL | EOL |
| 5.1 | 5.1.0 | Oct 24, 2022 | Nov 21, 2022 | 1357 days past EOL | EOL |
| 5.2 | 5.2.0 | Nov 21, 2022 | Dec 15, 2022 | 1333 days past EOL | EOL |
| 5.3 | 5.3.0 | Dec 15, 2022 | Jan 26, 2023 | 1291 days past EOL | EOL |
| 5.4 | 5.4.0 | Jan 26, 2023 | Feb 16, 2023 | 1270 days past EOL | EOL |
| 5.5 | 5.5.0 | Feb 16, 2023 | Mar 24, 2023 | 1234 days past EOL | EOL |
| 5.6 | 5.6.0 | Mar 24, 2023 | Apr 20, 2023 | 1207 days past EOL | EOL |
| 5.7 | 5.7.0 | Apr 20, 2023 | May 16, 2023 | 1181 days past EOL | EOL |
| 5.8 | 5.8.0 | May 16, 2023 | Jun 15, 2023 | 1151 days past EOL | EOL |
| 5.9 | 5.9.0 | Jun 15, 2023 | Jul 19, 2023 | 1117 days past EOL | EOL |
| 5.10 | 5.10.0 | Jul 19, 2023 | Aug 15, 2023 | 1090 days past EOL | EOL |
| 5.11 | 5.11.0 | Aug 14, 2023 | Sep 14, 2023 | 1060 days past EOL | EOL |
| 5.12 | 5.12.0 | Sep 15, 2023 | Oct 23, 2023 | 1021 days past EOL | EOL |
| 5.13 | 5.13.0 | Oct 23, 2023 | Nov 24, 2023 | 989 days past EOL | EOL |
| 5.14 | 5.14.0 | Nov 24, 2023 | Dec 15, 2023 | 968 days past EOL | EOL |
| 5.15 | 5.15.0 | Dec 15, 2023 | Jan 22, 2024 | 930 days past EOL | EOL |
| 5.16 | 5.16.0 | Jan 22, 2024 | Feb 23, 2024 | 898 days past EOL | EOL |
| 5.17 | 5.17.0 | Feb 23, 2024 | Mar 13, 2024 | 879 days past EOL | EOL |
| 5.18 | 5.18.1 | Mar 13, 2024 | Apr 12, 2024 | 849 days past EOL | EOL |
| 5.19 | 5.19.0 | Apr 12, 2024 | May 23, 2024 | 808 days past EOL | EOL |
| 5.20 | 5.20.0 | May 23, 2024 | Jun 28, 2024 | 772 days past EOL | EOL |
| 5.21 | 5.21.2 | Jun 28, 2024 | Jul 24, 2024 | 746 days past EOL | EOL |
| 5.22 | 5.22.0 | Jul 24, 2024 | Aug 22, 2024 | 717 days past EOL | EOL |
| 5.23 | 5.23.0 | Aug 22, 2024 | Sep 27, 2024 | 681 days past EOL | EOL |
| 5.24 | 5.24.2 | Sep 27, 2024 | Oct 31, 2024 | 647 days past EOL | EOL |
| 5.25 | 5.25.1 | Oct 31, 2024 | Dec 6, 2024 | 611 days past EOL | EOL |
| 5.26 LTS | 5.26.29 | Dec 6, 2024 | Jun 6, 2028 | 667 days remaining | Active |
| 2025.01 | 2025.01.0 | Feb 6, 2025 | Feb 27, 2025 | 528 days past EOL | EOL |
| 2025.02 | 2025.02.0 | Feb 27, 2025 | Mar 27, 2025 | 500 days past EOL | EOL |
| 2025.03 | 2025.03.0 | Mar 27, 2025 | Apr 30, 2025 | 466 days past EOL | EOL |
| 2025.04 | 2025.04.0 | Apr 30, 2025 | Jun 3, 2025 | 432 days past EOL | EOL |
| 2025.05 | 2025.05.1 | Jun 3, 2025 | Jul 2, 2025 | 403 days past EOL | EOL |
| 2025.06 | 2025.06.2 | Jul 2, 2025 | Jul 31, 2025 | 374 days past EOL | EOL |
| 2025.07 | 2025.07.1 | Jul 31, 2025 | Aug 15, 2025 | 359 days past EOL | EOL |
| 2025.08 | 2025.08.0 | Aug 27, 2025 | Sep 29, 2025 | 314 days past EOL | EOL |
| 2025.09 | 2025.09.0 | Sep 29, 2025 | Oct 30, 2025 | 283 days past EOL | EOL |
| 2025.10 | 2025.10.1 | Oct 30, 2025 | Dec 19, 2025 | 233 days past EOL | EOL |
| 2025.11 | 2025.11.2 | Dec 19, 2025 | Jan 16, 2026 | 205 days past EOL | EOL |
| 2025.12 | 2025.12.1 | Jan 16, 2026 | Feb 3, 2026 | 187 days past EOL | EOL |
| 2026.01 | 2026.01.4 | Feb 10, 2026 | Mar 6, 2026 | 156 days past EOL | EOL |
| 2026.02 | 2026.02.3 | Mar 20, 2026 | Apr 2, 2026 | 129 days past EOL | EOL |
| 2026.03 | 2026.03.1 | Apr 2, 2026 | Apr 23, 2026 | 108 days past EOL | EOL |
| 2026.04 | 2026.04.0 | Apr 23, 2026 | May 28, 2026 | 73 days past EOL | EOL |
| 2026.05 | 2026.05.0 | May 28, 2026 | Jul 8, 2026 | 32 days past EOL | EOL |
| 2026.06 | 2026.06.0 | Jul 8, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/neo4j)
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.
Your options when Neo4j reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
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.
Neo4j has 67 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Neo4j exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.