Rails End of Life Dates
framework
Developers rely on the Rails framework to build robust and scalable web applications, and staying on top of its lifecycle is crucial for maintaining security and compatibility. Created in 2004 by David Heinemeier Hansson, Rails is currently maintained by the Rails Core Team, who work tirelessly to ensure the framework remains up-to-date and secure. By tracking Rails end-of-life dates, supported versions, and security patch timelines, developers can plan their upgrades and migrations with confidence, avoiding potential security vulnerabilities and compatibility issues that can arise from using outdated software.
The Rails framework has undergone significant development over the years, resulting in a total of 11 versions, out of which 8 have already reached their end-of-life. Currently, 3 versions remain active, with the latest stable version being 7.2.3.1. However, version 7.2 is set to expire on 2026-08-09, marking the next significant milestone in the Rails lifecycle. The most recent end-of-life date was 2025-10-01, when version 7.1 reached the end of its support period. By keeping track of these dates, developers can ensure they are using supported versions and plan their upgrades accordingly.
With no tracked CVEs and zero critical vulnerabilities, the security picture for Rails appears to be relatively stable. As a result, there is no most affected version to report, and no Known Exploited Vulnerabilities (KEV) status to consider. Nevertheless, developers should remain vigilant and continue to monitor the framework's security landscape, ensuring they are always running the latest supported version to minimize potential risks. By staying informed about upcoming end-of-life dates and security patches, developers can maintain the integrity and security of their applications, safeguarding their users' data and trust.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 8.1 | Oct 22, 2025 | Oct 10, 2026 | Oct 10, 2027 | in 398d | 8.1.3.1 | — | Active | |
| 8.0 | Nov 7, 2024 | May 7, 2026 | Nov 7, 2026 | in 61d | 8.0.5.1 | — | EOL soon | |
| 7.2 | Aug 9, 2024 | Aug 9, 2025 | Aug 9, 2026 | 29d ago | 7.2.3.2 | — | EOL | |
| 7.1 | Oct 5, 2023 | Oct 1, 2024 | Oct 1, 2025 | 341d ago | 7.1.6 | — | EOL | |
| 7.0 | Dec 15, 2021 | Oct 15, 2023 | Apr 1, 2025 | 524d ago | 7.0.10 | — | EOL | |
| 6.1 | Dec 9, 2020 | Dec 15, 2021 | Oct 1, 2024 | 706d ago | 6.1.7.10 | — | EOL | |
| 6.0 | Aug 16, 2019 | Dec 15, 2021 | Jun 1, 2023 | 1194d ago | 6.0.6.1 | — | EOL | |
| 5.2 | Apr 9, 2018 | Dec 15, 2021 | Jun 1, 2022 | 1559d ago | 5.2.8.1 | — | EOL | |
| 5.1 | Apr 27, 2017 | Apr 9, 2018 | Aug 25, 2019 | 2570d ago | 5.1.7 | — | EOL | |
| 5.0 | Jun 30, 2016 | Apr 9, 2018 | Apr 9, 2018 | 3073d ago | 5.0.7.2 | — | EOL | |
| 4.2 | Dec 19, 2014 | Jun 30, 2016 | Apr 27, 2017 | 3420d ago | 4.2.11.3 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
