← ← Back to all products
Neo4j
Active
Databases Latest Version: 2026.05.0 Latest Release: May 26, 2026
Neo4j is the leading graph database platform for connected data and relationship-rich queries.
Versions
68
Latest Version
2026.05.0
Active Support
2
EOL
66
Lifecycle Timeline
Today ↓
2026.05
2026.05
2026.04
2026.04
2026.03
2026.03
2026.02
2026.02
2026.01
2026.01
2025.12
2025.12
2025.11
2025.11
2025.10
2025.10
2025.09
2025.09
2025.08
2025.08
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2026.05 | May 28, 2026 | Yes | No | 2026.05.0 | No | Active |
| 2026.04 | Apr 23, 2026 | No | May 28, 2026 | 2026.04.0 | No | EOL |
| 2026.03 | Apr 2, 2026 | No | Apr 23, 2026 | 2026.03.1 | No | EOL |
| 2026.02 | Mar 20, 2026 | No | Apr 2, 2026 | 2026.02.3 | No | EOL |
| 2026.01 | Feb 10, 2026 | No | Mar 6, 2026 | 2026.01.4 | No | EOL |
| 2025.12 | Jan 16, 2026 | No | Feb 3, 2026 | 2025.12.1 | No | EOL |
| 2025.11 | Dec 19, 2025 | No | Jan 16, 2026 | 2025.11.2 | No | EOL |
| 2025.10 | Oct 30, 2025 | No | Dec 19, 2025 | 2025.10.1 | No | EOL |
| 2025.09 | Sep 29, 2025 | No | Oct 30, 2025 | 2025.09.0 | No | EOL |
| 2025.08 | Aug 27, 2025 | No | Sep 29, 2025 | 2025.08.0 | No | EOL |
| 2025.07 | Jul 31, 2025 | No | Aug 15, 2025 | 2025.07.1 | No | EOL |
| 2025.06 | Jul 2, 2025 | No | Jul 31, 2025 | 2025.06.2 | No | EOL |
| 2025.05 | Jun 3, 2025 | No | Jul 2, 2025 | 2025.05.1 | No | EOL |
| 2025.04 | Apr 30, 2025 | No | Jun 3, 2025 | 2025.04.0 | No | EOL |
| 2025.03 | Mar 27, 2025 | No | Apr 30, 2025 | 2025.03.0 | No | EOL |
| 2025.02 | Feb 27, 2025 | No | Mar 27, 2025 | 2025.02.0 | No | EOL |
| 2025.01 | Feb 6, 2025 | No | Feb 27, 2025 | 2025.01.0 | No | EOL |
| 5.26 | Dec 6, 2024 | Yes | Jun 6, 2028 | 5.26.26 | Yes | Active |
| 5.25 | Oct 31, 2024 | No | Dec 6, 2024 | 5.25.1 | No | EOL |
| 5.24 | Sep 27, 2024 | No | Oct 31, 2024 | 5.24.2 | No | EOL |
| 5.23 | Aug 22, 2024 | No | Sep 27, 2024 | 5.23.0 | No | EOL |
| 5.22 | Jul 24, 2024 | No | Aug 22, 2024 | 5.22.0 | No | EOL |
| 5.21 | Jun 28, 2024 | No | Jul 24, 2024 | 5.21.2 | No | EOL |
| 5.20 | May 23, 2024 | No | Jun 28, 2024 | 5.20.0 | No | EOL |
| 5.19 | Apr 12, 2024 | No | May 23, 2024 | 5.19.0 | No | EOL |
| 5.18 | Mar 13, 2024 | No | Apr 12, 2024 | 5.18.1 | No | EOL |
| 5.17 | Feb 23, 2024 | No | Mar 13, 2024 | 5.17.0 | No | EOL |
| 5.16 | Jan 22, 2024 | No | Feb 23, 2024 | 5.16.0 | No | EOL |
| 5.15 | Dec 15, 2023 | No | Jan 22, 2024 | 5.15.0 | No | EOL |
| 5.14 | Nov 24, 2023 | No | Dec 15, 2023 | 5.14.0 | No | EOL |
| 5.13 | Oct 23, 2023 | No | Nov 24, 2023 | 5.13.0 | No | EOL |
| 5.12 | Sep 15, 2023 | No | Oct 23, 2023 | 5.12.0 | No | EOL |
| 5.11 | Aug 14, 2023 | No | Sep 14, 2023 | 5.11.0 | No | EOL |
| 5.10 | Jul 19, 2023 | No | Aug 15, 2023 | 5.10.0 | No | EOL |
| 5.9 | Jun 15, 2023 | No | Jul 19, 2023 | 5.9.0 | No | EOL |
| 5.8 | May 16, 2023 | No | Jun 15, 2023 | 5.8.0 | No | EOL |
| 5.7 | Apr 20, 2023 | No | May 16, 2023 | 5.7.0 | No | EOL |
| 5.6 | Mar 24, 2023 | No | Apr 20, 2023 | 5.6.0 | No | EOL |
| 5.5 | Feb 16, 2023 | No | Mar 24, 2023 | 5.5.0 | No | EOL |
| 5.4 | Jan 26, 2023 | No | Feb 16, 2023 | 5.4.0 | No | EOL |
| 5.3 | Dec 15, 2022 | No | Jan 26, 2023 | 5.3.0 | No | EOL |
| 5.2 | Nov 21, 2022 | No | Dec 15, 2022 | 5.2.0 | No | EOL |
| 5.1 | Oct 24, 2022 | No | Nov 21, 2022 | 5.1.0 | No | EOL |
| 4.4 | Dec 2, 2021 | No | Nov 30, 2025 | 4.4.48 | Yes | EOL |
| 4.3 | Jun 17, 2021 | No | Dec 16, 2022 | 4.3.23 | No | EOL |
| 4.2 | Nov 17, 2020 | No | May 16, 2022 | 4.2.19 | No | EOL |
| 4.1 | Jun 23, 2020 | No | Dec 22, 2021 | 4.1.12 | No | EOL |
| 4.0 | Jan 15, 2020 | No | Jul 14, 2021 | 4.0.12 | No | EOL |
| 3.5 | Nov 29, 2018 | No | May 27, 2022 | 3.5.35 | No | EOL |
| 3.4 | May 17, 2018 | No | Mar 31, 2020 | 3.4.18 | No | EOL |
| 3.3 | Oct 24, 2017 | No | Apr 28, 2019 | 3.3.9 | No | EOL |
| 3.2 | May 11, 2017 | No | Nov 30, 2018 | 3.2.14 | No | EOL |
| 3.1 | Dec 13, 2016 | No | Jun 13, 2018 | 3.1.9 | No | EOL |
| 3.0 | Apr 16, 2016 | No | Oct 31, 2017 | 3.0.12 | No | EOL |
| 2.3 | Oct 21, 2015 | No | Apr 21, 2017 | 2.3.12 | No | EOL |
| 2.2 | Mar 25, 2015 | No | Sep 25, 2016 | 2.2.10 | No | EOL |
| 2.1 | May 29, 2014 | No | Nov 29, 2015 | 2.1.8 | No | EOL |
| 2.0 | Dec 11, 2013 | No | Jun 11, 2015 | 2.0.5 | No | EOL |
| 1.9 | May 21, 2013 | No | Nov 21, 2014 | 1.9.9 | No | EOL |
| 1.8 | Sep 28, 2012 | No | Mar 28, 2014 | 1.8.3 | No | EOL |
| 1.7 | Apr 18, 2012 | No | Oct 18, 2013 | 1.7.2 | No | EOL |
| 1.6 | Jan 22, 2012 | No | Jul 22, 2013 | 1.6.3 | No | EOL |
| 1.5 | Nov 9, 2011 | No | Mar 9, 2013 | 1.5.3 | No | EOL |
| 1.4 | Jul 8, 2011 | No | Jan 8, 2013 | 1.4.2 | No | EOL |
| 1.3 | Apr 12, 2011 | No | Sep 12, 2012 | 1.3.0 | No | EOL |
| 1.2 | Dec 29, 2010 | No | Jun 29, 2012 | 1.2.0 | No | EOL |
| 1.1 | Jul 30, 2010 | No | Jan 30, 2012 | 1.1.0 | No | EOL |
| 1.0 | Feb 23, 2010 | No | Aug 23, 2011 | 1.0.0 | No | EOL |
Frequently Asked Questions
Which versions of Neo4j have reached end of life?
The following Neo4j versions have reached end of life and no longer receive security updates: 2026.04, 2026.03, 2026.02, 2026.01, 2025.12, 2025.11, 2025.10, 2025.09 (and 58 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Neo4j 2026.04?
Neo4j 2026.04 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Neo4j?
The latest version of Neo4j is 2026.05.0, released in the 2026.05 release cycle.
How many versions of Neo4j are currently supported?
Neo4j currently has 2 actively supported version(s): 2026.05, 5.26.
When does Neo4j 2026.05 reach end of life?
Neo4j 2026.05 does not have a specific end-of-life date announced yet.
What should I do when Neo4j reaches end of life?
When a Neo4j version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.