Neo4j End of Life (EOL) Dates and End of Support (EOS) Dates
Neo4j end of life (EOL) and end of support (EOS) dates: 71 Neo4j versions have reached EOL, including Neo4j 2026.09 (EOL date: Oct 20, 2026) — no longer receiving security updates or patches. Neo4j 2026.10.2 is the current supported release — 2 versions in active support. Also see Jenkins lifecycle dates for related end-of-life information.
Currently Supported Neo4j Releases - Active EOS/EOSL Support (2)
Neo4j End of Life (EOL) Releases - No Longer Supported (71)
| Release | Released | Support Status | Latest | LTS |
|---|---|---|---|---|
| 2026.09 | (2 months ago) | (1 month and 1 day ago) | 2026.09.0 (2 months ago) | - |
| 2026.08 | (2 months ago) | (2 months ago) | 2026.08.1 (2 months ago) | - |
| 2026.07 | (3 months ago) | (2 months ago) | 2026.07.1 (3 months ago) | - |
| 2026.06 | (4 months ago) | (3 months ago) | 2026.06.0 (4 months ago) | - |
| 2026.05 | (5 months ago) | (4 months ago) | 2026.05.0 (5 months ago) | - |
| 2026.04 | (6 months ago) | (5 months ago) | 2026.04.0 (6 months ago) | - |
| 2026.03 | (7 months ago) | (6 months ago) | 2026.03.1 (7 months ago) | - |
| 2026.02 | (8 months ago) | (7 months ago) | 2026.02.3 (8 months ago) | - |
| 2026.01 | (9 months ago) | (8 months ago) | 2026.01.4 (9 months ago) | - |
| 2025.12 | (10 months ago) | (9 months ago) | 2025.12.1 (10 months ago) | - |
| 2025.11 | (11 months ago) | (10 months ago) | 2025.11.2 (11 months ago) | - |
| 2025.10 | (1 year ago) | (11 months ago) | 2025.10.1 (1 year ago) | - |
| 2025.09 | (1 year and 1 month ago) | (1 year ago) | 2025.09.0 (1 year and 2 months ago) | - |
| 2025.08 | (1 year and 2 months ago) | (1 year and 1 month ago) | 2025.08.0 (1 year and 3 months ago) | - |
| 2025.07 | (1 year and 3 months ago) | (1 year and 3 months ago) | 2025.07.1 (1 year and 3 months ago) | - |
| 2025.06 | (1 year and 4 months ago) | (1 year and 3 months ago) | 2025.06.2 (1 year and 4 months ago) | - |
| 2025.05 | (1 year and 5 months ago) | (1 year and 4 months ago) | 2025.05.1 (1 year and 5 months ago) | - |
| 2025.04 | (1 year and 6 months ago) | (1 year and 5 months ago) | 2025.04.0 (1 year and 7 months ago) | - |
| 2025.03 | (1 year and 7 months ago) | (1 year and 6 months ago) | 2025.03.0 (1 year and 8 months ago) | - |
| 2025.02 | (1 year and 8 months ago) | (1 year and 7 months ago) | 2025.02.0 (1 year and 8 months ago) | - |
| 2025.01 | (1 year and 9 months ago) | (1 year and 8 months ago) | 2025.01.0 (1 year and 9 months ago) | - |
| 5.25 | (2 years ago) | (1 year and 11 months ago) | 5.25.1 (2 years ago) | - |
| 5.24 | (2 years and 1 month ago) | (2 years ago) | 5.24.2 (2 years and 1 month ago) | - |
| 5.23 | (2 years and 2 months ago) | (2 years and 1 month ago) | 5.23.0 (2 years and 2 months ago) | - |
| 5.22 | (2 years and 3 months ago) | (2 years and 2 months ago) | 5.22.0 (2 years and 4 months ago) | - |
| 5.21 | (2 years and 4 months ago) | (2 years and 3 months ago) | 5.21.2 (2 years and 4 months ago) | - |
| 5.20 | (2 years and 5 months ago) | (2 years and 4 months ago) | 5.20.0 (2 years and 5 months ago) | - |
| 5.19 | (2 years and 7 months ago) | (2 years and 5 months ago) | 5.19.0 (2 years and 7 months ago) | - |
| 5.18 | (2 years and 8 months ago) | (2 years and 7 months ago) | 5.18.1 (2 years and 8 months ago) | - |
| 5.17 | (2 years and 8 months ago) | (2 years and 8 months ago) | 5.17.0 (2 years and 8 months ago) | - |
| 5.16 | (2 years and 9 months ago) | (2 years and 8 months ago) | 5.16.0 (2 years and 9 months ago) | - |
| 5.15 | (2 years and 11 months ago) | (2 years and 9 months ago) | 5.15.0 (2 years and 11 months ago) | - |
| 5.14 | (2 years and 11 months ago) | (2 years and 11 months ago) | 5.14.0 (2 years and 11 months ago) | - |
| 5.13 | (3 years ago) | (2 years and 11 months ago) | 5.13.0 (3 years ago) | - |
| 5.12 | (3 years and 2 months ago) | (3 years ago) | 5.12.0 (3 years and 2 months ago) | - |
| 5.11 | (3 years and 3 months ago) | (3 years and 2 months ago) | 5.11.0 (3 years and 3 months ago) | - |
| 5.10 | (3 years and 4 months ago) | (3 years and 3 months ago) | 5.10.0 (3 years and 4 months ago) | - |
| 5.9 | (3 years and 5 months ago) | (3 years and 4 months ago) | 5.9.0 (3 years and 5 months ago) | - |
| 5.8 | (3 years and 6 months ago) | (3 years and 5 months ago) | 5.8.0 (3 years and 6 months ago) | - |
| 5.7 | (3 years and 7 months ago) | (3 years and 6 months ago) | 5.7.0 (3 years and 7 months ago) | - |
| 5.6 | (3 years and 7 months ago) | (3 years and 7 months ago) | 5.6.0 (3 years and 7 months ago) | - |
| 5.5 | (3 years and 9 months ago) | (3 years and 7 months ago) | 5.5.0 (3 years and 9 months ago) | - |
| 5.4 | (3 years and 9 months ago) | (3 years and 9 months ago) | 5.4.0 (3 years and 9 months ago) | - |
| 5.3 | (3 years and 11 months ago) | (3 years and 9 months ago) | 5.3.0 (3 years and 11 months ago) | - |
| 5.2 | (4 years ago) | (3 years and 11 months ago) | 5.2.0 (4 years ago) | - |
| 5.1 | (4 years ago) | (4 years ago) | 5.1.0 (4 years and 1 month ago) | - |
| 4.4 (LTS) | (4 years and 11 months ago) | (11 months ago) | 4.4.48 (9 months ago) | LTS |
| 4.3 | (5 years and 5 months ago) | (3 years and 11 months ago) | 4.3.23 (3 years and 11 months ago) | - |
| 4.2 | (6 years ago) | (4 years and 6 months ago) | 4.2.19 (4 years and 3 months ago) | - |
| 4.1 | (6 years and 4 months ago) | (4 years and 10 months ago) | 4.1.12 (4 years and 3 months ago) | - |
| 4.0 | (6 years and 10 months ago) | (5 years and 4 months ago) | 4.0.12 (5 years and 4 months ago) | - |
| 3.5 | (7 years and 11 months ago) | (4 years and 5 months ago) | 3.5.35 (4 years and 3 months ago) | - |
| 3.4 | (8 years and 6 months ago) | (6 years and 7 months ago) | 3.4.18 (6 years and 6 months ago) | - |
| 3.3 | (9 years ago) | (7 years and 6 months ago) | 3.3.9 (8 years ago) | - |
| 3.2 | (9 years and 6 months ago) | (7 years and 11 months ago) | 3.2.14 (7 years and 8 months ago) | - |
| 3.1 | (9 years and 11 months ago) | (8 years and 5 months ago) | 3.1.9 (8 years and 5 months ago) | - |
| 3.0 | (10 years and 7 months ago) | (9 years ago) | 3.0.12 (9 years and 1 month ago) | - |
| 2.3 | (11 years and 1 month ago) | (9 years and 7 months ago) | 2.3.12 (8 years and 11 months ago) | - |
| 2.2 | (11 years and 7 months ago) | (10 years and 1 month ago) | 2.2.10 (10 years and 5 months ago) | - |
| 2.1 | (12 years and 5 months ago) | (10 years and 11 months ago) | 2.1.8 (11 years and 7 months ago) | - |
| 2.0 | (12 years and 11 months ago) | (11 years and 5 months ago) | 2.0.5 (11 years and 6 months ago) | - |
| 1.9 | (13 years and 6 months ago) | (12 years ago) | 1.9.9 (12 years and 1 month ago) | - |
| 1.8 | (14 years and 1 month ago) | (12 years and 7 months ago) | 1.8.3 (13 years and 4 months ago) | - |
| 1.7 | (14 years and 7 months ago) | (13 years and 1 month ago) | 1.7.2 (14 years ago) | - |
| 1.6 | (14 years and 9 months ago) | (13 years and 3 months ago) | 1.6.3 (14 years ago) | - |
| 1.5 | (15 years ago) | (13 years and 8 months ago) | 1.5.3 (14 years ago) | - |
| 1.4 | (15 years and 4 months ago) | (13 years and 10 months ago) | 1.4.2 (14 years ago) | - |
| 1.3 | (15 years and 7 months ago) | (14 years and 2 months ago) | 1.3.0 (15 years and 7 months ago) | - |
| 1.2 | (15 years and 10 months ago) | (14 years and 4 months ago) | 1.2.0 (15 years and 10 months ago) | - |
| 1.1 | (16 years and 3 months ago) | (14 years and 9 months ago) | 1.1.0 (16 years and 3 months ago) | - |
| 1.0 | (16 years and 8 months ago) | (15 years and 2 months ago) | 1.0.0 (16 years and 8 months ago) | - |
Your Neo4j end of life date decides when a graph database stops getting fixes, so the support status of your exact version matters before you plan a move. Neo4j 5.26 LTS is covered through June 2028, while version 4.4 ended on 30 November 2025.
Neo4j End of Life Dates by Version
Each end-of-life date below follows the Enterprise Edition and comes from endoflife.date, last updated 10 October 2026. A row marked Ended no longer receives patches.
| Version | Released | Status |
|---|---|---|
| 3.5 | 29 Nov 2018 | Ended 27 May 2022 |
| 4.0 | 15 Jan 2020 | Ended 14 Jul 2021 |
| 4.1 | 23 Jun 2020 | Ended 22 Dec 2021 |
| 4.2 | 17 Nov 2020 | Ended 16 May 2022 |
| 4.3 | 17 Jun 2021 | Ended 16 Dec 2022 |
| 4.4 LTS | 2 Dec 2021 | Ended 30 Nov 2025 |
| 5.25 | 31 Oct 2024 | Ended 6 Dec 2024 |
| 2026.08 | 10 Sep 2026 | Ended 21 Sep 2026 |
| 5.26 LTS | 6 Dec 2024 | Supported until 6 Jun 2028 |
| 2026.09 | 21 Sep 2026 | Supported at that update |
Every older line is past its end, and Neo4j 6 never arrived: the old scheme would have introduced it after 5.26. Neo4j 5 therefore became the base for everything that followed.
Neo4j 5.26 LTS Is Supported Until June 2028
The LTS release 5.26 is the last Neo4j 5 version, shipped in December 2024. It receives critical patches and security updates but no new features, which makes it the stable choice for production teams that don't want monthly change.
Neo4j 5.26 Patch Releases and Bug Fixes
Recent 5.26 builds are bug fixes and security patches. The latest patch release, 5.26.32, landed on 9 October 2026; 5.26.30 upgraded Bouncy Castle for CVE-2025-14813, and 5.26.31 escaped dangerous unicode in the plain text query log.
Support Terms for Enterprise, Community and AuraDB
Neo4j's support terms vary by edition. Dates here track the Enterprise Edition, whose customers receive patches until each end date. Fixes aren't guaranteed for the Community Edition, a single-node build with no clustering. AuraDB is the hosted cloud service and updates itself: Aura Professional has a support portal without an SLA, and the top Aura tier adds premium ticket-based help with one. Because each Aura database updates itself, an end date rarely applies there.
Calendar Versioning and Supported Versions
Neo4j 2025 releases began a new scheme: Neo4j follows calendar versioning instead of semver, starting with 2025.01, which allows online upgrades from 5.26. Only the latest minor version is supported, so each monthly build ends when the next arrives. The latest version is 2026.10.1, from 23 October 2026.
Neo4j 2026 Monthly Releases
Neo4j 2026 builds ship monthly: 2026.10.0 on 20 October, then 2026.10.1 three days later. Anyone still on 2026.09 should move on, since the tracker may lag the real release. Each move means rechecking your Cypher queries and drivers, and a build is unsupported once the next one ships.
Neo4j 4.4 End of Support
Each 4.x minor was supported for 18 months from its GA date, except the last, 4.4, which got 36 months. Its end moved from 30 June to 30 November 2025; check your drivers against the compatibility list on the Neo4j support site.
Long-Term Support for Cypher 5 and Cypher 25
The query language has its own lifecycle. Since 2025.06 a database offers two Cypher versions, decoupled from the server, so a server move needs no query migration. That separation lets a production database stay on stable Cypher.
Cypher 5
Cypher 5 is frozen: only bug fixes, performance work and patches. Existing databases stay on it after a move for backward compatibility, and Neo4j promises a year's notice before Cypher 5 ends. Cypher 5 stays available on at least two more LTS releases, roughly three to four years out.
Cypher 25
Cypher 25 gets new features each server release, such as conditional updating. Only additive changes are allowed, though some deprecated Cypher 5 features were dropped. Prefix a query with CYPHER 25 to opt in. It is the feature-rich line that keeps evolving after Cypher 5 ends, and Cypher performance still improves with runtime updates whichever version runs.
Release Notes to Read Before You Upgrade
Read the release notes first, then plan your migration and note any breaking change that touches your database. A version nearing its end date should be moved first. Run call dbms.components() yield versions unwind versions as version return version; to confirm what you run. Neo4j Bloom, Graph Data Science and Ops Manager publish separate notes: GDS 2026.10 pairs with Neo4j 2026.10.
Neo4j 5 Upgrade Checklist
Use these steps when moving a 5.x system onto 5.26 or a 2026 release before its current line stops being supported:
- Switch cluster discovery from V1 to V2.
- Convert store formats to block.
- Enable JSON logging.
- Test a rolling upgrade in staging before the graph database goes live.