Amazon Neptune End of Life Dates
other
Developers rely on Amazon Neptune to efficiently manage and track the end-of-life dates of various software releases, ensuring timely upgrades and minimizing potential security risks. Created to provide a centralized platform for monitoring supported versions and security patch timelines, this tool has become an essential resource for teams seeking to stay ahead of end-of-life milestones. Maintained by a team of experts, Amazon Neptune is continually updated to reflect the latest information on software releases, allowing developers to plan and execute upgrades with confidence. With a history of providing accurate and reliable data, Amazon Neptune has established itself as a trusted companion for developers navigating the complex landscape of software lifecycles.
The Amazon Neptune ecosystem comprises a total of 35 versions, with 10 of these having already reached their end-of-life. Currently, 25 versions remain active, including the latest stable version, 1.1.1.0.R7. As the landscape continues to evolve, developers must remain vigilant, particularly with the next end-of-life date approaching on 2026-06-30, at which point version 1.1.1.0 will no longer be supported. This milestone serves as a reminder of the importance of proactive planning and upgrading to ensure uninterrupted support and access to security patches. The most recent end-of-life date was 2025-03-15, when version 1.1.0.0 reached the end of its support cycle, underscoring the need for ongoing monitoring and adaptability.
From a security perspective, Amazon Neptune presents a favorable picture, with a total of 0 CVEs tracked and no critical vulnerabilities reported. As a result, there is no most affected version, and the KEV status is not applicable in this context. Despite this positive outlook, developers should remain cautious and continue to monitor the situation, as the security landscape can change rapidly. By staying informed and taking proactive measures, such as upgrading to the latest stable version and regularly reviewing security patch timelines, developers can minimize potential risks and ensure the continued security and integrity of their systems.
Last updated: Oct 23, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 1.5.0.0 | Oct 13, 2026 | — | No | — | 1.5.0.0 | — | Active | |
| 1.4.8.1 | Sep 30, 2026 | — | Oct 27, 2027 | in 369d | 1.4.8.1 | — | Active | |
| 1.4.7.1 | Sep 16, 2026 | — | Jun 3, 2027 | in 223d | 1.4.7.1 | — | Active | |
| 1.4.8.0 | Jul 27, 2026 | — | Oct 27, 2027 | in 369d | 1.4.8.0 | — | Active | |
| 1.4.7.0 | Mar 3, 2026 | — | Jun 3, 2027 | in 223d | 1.4.7.0 | — | Active | |
| 1.4.6.3 | Dec 18, 2025 | — | Jun 3, 2027 | in 223d | 1.4.6.3 | — | Active | |
| 1.4.6.2 | Nov 18, 2025 | — | Jun 3, 2027 | in 223d | 1.4.6.2 | — | Active | |
| 1.4.6.1 | Sep 18, 2025 | — | Mar 6, 2027 | in 134d | 1.4.6.1 | — | Active | |
| 1.4.6.0 | Sep 2, 2025 | — | Mar 6, 2027 | in 134d | 1.4.6.0 | — | Active | |
| 1.4.5.1 | Jun 30, 2025 | — | Mar 6, 2027 | in 134d | 1.4.5.1 | — | Active | |
| 1.4.5.0 | Apr 9, 2025 | — | Mar 6, 2027 | in 134d | 1.4.5.0 | — | Active | |
| 1.4.4.0 | Feb 24, 2025 | — | Mar 6, 2027 | in 134d | 1.4.4.0 | — | Active | |
| 1.4.3.0 | Jan 21, 2025 | — | Mar 6, 2027 | in 134d | 1.4.3.0 | — | Active | |
| 1.4.2.0 | Dec 19, 2024 | — | Mar 6, 2027 | in 134d | 1.4.2.0 | — | Active | |
| 1.4.1.0 | Nov 21, 2024 | — | Mar 6, 2027 | in 134d | 1.4.1.0 | — | Active | |
| 1.4.0.0 | Nov 6, 2024 | — | Mar 6, 2027 | in 134d | 1.4.0.0 | — | Active | |
| 1.3.4.0 | Oct 1, 2024 | — | Mar 6, 2027 | in 134d | 1.3.4.0 | — | Active | |
| 1.3.3.0 | Aug 5, 2024 | — | Mar 6, 2027 | in 134d | 1.3.3.0 | — | Active | |
| 1.2.1.2 | Aug 5, 2024 | — | Dec 4, 2026 | in 42d | 1.2.1.2 | — | EOL soon | |
| 1.3.2.1 | Jun 20, 2024 | — | Mar 6, 2027 | in 134d | 1.3.2.1 | — | Active | |
| 1.3.2.0 | Jun 6, 2024 | — | Mar 6, 2027 | in 134d | 1.3.2.0 | — | Active | |
| 1.2.1.1 | Mar 11, 2024 | — | Dec 4, 2026 | in 42d | 1.2.1.1 | — | EOL soon | |
| 1.3.1.0 | Mar 6, 2024 | — | Mar 6, 2027 | in 134d | 1.3.1.0 | — | Active | |
| 1.3.0.0 | Nov 15, 2023 | — | Mar 6, 2027 | in 134d | 1.3.0.0 | — | Active | |
| 1.2.1.0 | Mar 8, 2023 | — | Dec 4, 2026 | in 42d | 1.2.1.0.R7 | — | EOL soon | |
| 1.2.0.2 | Nov 20, 2022 | — | Dec 4, 2026 | in 42d | 1.2.0.2.R6 | — | EOL soon | |
| 1.2.0.1 | Oct 26, 2022 | — | Dec 4, 2026 | in 42d | 1.2.0.1.R3 | — | EOL soon | |
| 1.2.0.0 | Jul 21, 2022 | — | Dec 4, 2026 | in 42d | 1.2.0.0.R4 | — | EOL soon | |
| 1.1.1.0 | Apr 19, 2022 | — | Dec 4, 2026 | in 42d | 1.1.1.0.R7 | — | EOL soon | |
| 1.1.0.0 | Nov 19, 2021 | — | Mar 15, 2025 | 587d ago | 1.1.0.0.R3 | — | EOL | |
| 1.0.5.1 | Oct 1, 2021 | — | Jan 30, 2023 | 1362d ago | 1.0.5.1.R4 | — | EOL | |
| 1.0.5.0 | Jul 27, 2021 | — | Jan 30, 2023 | 1362d ago | 1.0.5.0.R5 | — | EOL | |
| 1.0.4.2 | Jun 1, 2021 | — | Jan 30, 2023 | 1362d ago | 1.0.4.2.R5 | — | EOL | |
| 1.0.4.1 | Dec 8, 2020 | — | Jan 30, 2023 | 1362d ago | 1.0.4.1.R1.1 | — | EOL | |
| 1.0.4.0 | Oct 12, 2020 | — | Jan 30, 2023 | 1362d ago | 1.0.4.0.R2 | — | EOL | |
| 1.0.3.0 | Aug 3, 2020 | — | Jan 30, 2023 | 1362d ago | 1.0.3.0.R3 | — | EOL | |
| 1.0.2.2 | Mar 9, 2020 | — | Jul 29, 2022 | 1547d ago | 1.0.2.2.R6 | — | EOL | |
| 1.0.2.1 | Nov 22, 2019 | — | Jul 29, 2022 | 1547d ago | 1.0.2.1.R6 | — | EOL | |
| 1.0.2.0 | Nov 8, 2019 | — | May 19, 2020 | 2348d ago | 1.0.2.0.R3 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
