Ruby on Rails EOL: support dates for every Rails version
Rails 8.0 lost security support on 7 November 2026 and Rails 7.2 on 9 August 2026. Only Rails 8.1 is supported now, with security fixes until 10 October 2027. OSSeva patches Rails 8.0 and 7.2 after end of life; other versions are assessed case by case. Dates checked against rubyonrails.org and endoflife.date on 19 November 2026.
- Latest release
- 8.1.4.1
- Supported lines
- 1
- End-of-life lines
- 10
- Next end of life
- 8.1 · 10 Oct 2027
Rails 7.2 and 8.0 have ended; 8.1 is the only supported series
Upgrade, or keep Rails 8.0 and 7.2 patched
Most applications should move to Rails 8.1. When a gem, a Ruby upgrade or a release freeze holds an application on 7.2 or 8.0, OSSeva patches both. Other Rails versions are assessed case by case. Critical fixes ship within 48 hours and High within 7 days.
Who patches Ruby on Rails after end of life
OSSeva provides Ruby on Rails extended support: patched, signed builds for Ruby on Rails 8.0 and 7.2 after upstream support ends, plus 24/7 operations on the Operate tier.
Ruby on Rails release timeline
All Ruby on Rails versions, release dates and end-of-life dates
| Version | Released | Active Support | Security Support | Latest | OSSeva |
|---|---|---|---|---|---|
| 8.1 | 1 year and 1 month ago(22 Oct 2025) | Ended 43 days ago(10 Oct 2026) | Ends in 11 months(10 Oct 2027) | 8.1.4.1 | – |
| 8.0 | 2 years ago(7 Nov 2024) | Ended 7 months ago(7 May 2026) | Ended 15 days ago(7 Nov 2026) | 8.0.5.2 | Patched |
| 7.2 | 2 years and 3 months ago(9 Aug 2024) | Ended 1 year and 3 months ago(9 Aug 2025) | Ended 3 months ago(9 Aug 2026) | 7.2.4 | Patched |
| 7.1 | 3 years and 2 months ago(5 Oct 2023) | Ended 2 years and 2 months ago(1 Oct 2024) | Ended 1 year and 2 months ago(1 Oct 2025) | 7.1.6 | – |
| 7.0 | 4 years and 11 months ago(15 Dec 2021) | Ended 3 years and 1 month ago(15 Oct 2023) | Ended 1 year and 8 months ago(1 Apr 2025) | 7.0.10 | – |
| 6.1 | 5 years and 11 months ago(9 Dec 2020) | Ended 4 years and 11 months ago(15 Dec 2021) | Ended 2 years and 2 months ago(1 Oct 2024) | 6.1.7.10 | – |
| 6.0 | 7 years and 3 months ago(16 Aug 2019) | Ended 4 years and 11 months ago(15 Dec 2021) | Ended 3 years and 6 months ago(1 Jun 2023) | 6.0.6.1 | – |
| 5.2 | 8 years and 7 months ago(9 Apr 2018) | Ended 4 years and 11 months ago(15 Dec 2021) | Ended 4 years and 6 months ago(1 Jun 2022) | 5.2.8.1 | – |
| 5.1 | 9 years and 7 months ago(27 Apr 2017) | Ended 8 years and 7 months ago(9 Apr 2018) | Ended 7 years and 3 months ago(25 Aug 2019) | 5.1.7 | – |
| 5.0 | 10 years and 5 months ago(30 Jun 2016) | Ended 8 years and 7 months ago(9 Apr 2018) | Ended 8 years and 7 months ago(9 Apr 2018) | 5.0.7.2 | – |
| 4.2 | 11 years and 11 months ago(19 Dec 2014) | Ended 10 years and 5 months ago(30 Jun 2016) | Ended 9 years and 7 months ago(27 Apr 2017) | 4.2.11.3 | – |
Lifecycle data from endoflife.date (MIT licence), refreshed 21 Nov 2026. Upstream policy: rubyonrails.org. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
Rails 7.2, 8.0 and 8.1 support dates
Rails 8.0 and 7.2 are past security support, and 8.1 is the only series the Rails team still fixes. The Rails maintenance policy splits support into new features, bug fixes and security issues: a minor release gets bug fixes for about a year and security fixes for two years after its first release. Once a series is unsupported, the maintenance page tells users they are responsible for their own bug and security fixes, and says backports may be published to git but no new versions will be released.
Rails support dates. Source: rubyonrails.org/maintenance (8.1 and 8.0), read on 19 November 2026; 7.2 from endoflife.date, because the page no longer lists it. Ruby versions from the gem metadata on rubygems.org.
| Series | Released | Bug fixes until | Security fixes until | Needs Ruby |
|---|---|---|---|---|
| Rails 7.2 | 9 Aug 2024 | 9 Aug 2025 | 9 Aug 2026 (ended) | 3.1.0 or newer |
| Rails 8.0 | 7 Nov 2024 | 7 May 2026 (ended) | 7 Nov 2026 (ended) | 3.2.0 or newer |
| Rails 8.1 | 22 Oct 2025 | 10 Oct 2026 (ended) | 10 Oct 2027 | 3.2.0 or newer |
Rails 8.1 bug-fix support also ended on 10 October 2026 per the page, so the only phase left for 8.1 is security fixes. The maintenance page has no separate severe-security category.
What changed when Rails 8.0 and 7.2 ended
Rails 8.0.5.2, released on 4 November 2026, is the last 8.0 security release on rubygems.org, three days before 8.0 support ended. Its advisories fixed a batch of issues, including CVE-2026-126186 (arbitrary file read and remote code execution in Active Storage, High, CVSS 8.8) and CVE-2026-126081 (Strong Parameters bypass in Parameters#each_key, High, CVSS 7.5). The advisories give the affected range as every release before 8.0.5.2, with fixes in 8.0.5.2 and 8.1.4.1 and none for 7.2, so an application on 7.2 has no upstream fix for them.
Rails 7.2 shows the other side. Its last security release, 7.2.3.2 on 29 July 2026, fixed CVE-2026-66066, a critical (CVSS 9.5) arbitrary file read and remote code execution in Active Storage variant processing when libvips operations marked unsafe were not disabled. A 7.2 application on 7.2.3.1 or earlier is in the affected range, and the fix is a gem update away. 7.2.4 followed on 24 September 2026, after the security window had closed.
The Ruby requirement decides the order of work. Rails 8.1 needs Ruby 3.2.0 or newer, so an application on Rails 7.2 and Ruby 3.1 has to upgrade Ruby first, and Ruby 3.2 itself ended on 1 April 2026. Moving from Rails 7.2 to 8.1 therefore means a Ruby upgrade, a Rails upgrade across two minor series and a gem audit, usually in that order. Keeping Rails 8.0 or 7.2 patched removes the deadline from that sequence without changing the framework version your code runs on.
Who patches Rails after end of life?
OSSeva patches Ruby on Rails 8.0 and 7.2 after end of life, and assesses other versions case by case through a version coverage check. The Rails team publishes no new versions for an unsupported series. Critical fixes ship within 48 hours and High within 7 days, and pricing is per application.
Running an end-of-life Ruby on Rails version?
OSSeva keeps end-of-life Ruby on Rails patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.
Ruby on Rails extended supportIs Rails 8.0 end of life?
Yes for security support. The Rails maintenance page lists Rails 8.0 with bug fixes until 7 May 2026 and security fixes until 7 November 2026, so it is past both. The last 8.0 release is 8.0.5.2 of 4 November 2026.
Is Rails 7.2 end of life?
Yes. Rails gives a minor release two years of security fixes, and Rails 7.2, released on 9 August 2024, reached that limit on 9 August 2026. The maintenance page no longer lists it.
When does Rails 8.1 reach end of life?
Security fixes for Rails 8.1 run until 10 October 2027 per the Rails maintenance page. Its bug-fix support ended on 10 October 2026.
What is the difference between Rails bug fixes and security fixes?
Rails lists them as separate support groups. A minor release gets bug fixes for about a year and security fixes for two years after release, so a series can be past bug-fix support and still receive security releases, as Rails 8.0 did between 7 May and 7 November 2026.
Which Ruby version does Rails 8.0 need?
Ruby 3.2.0 or newer, per the gem metadata on rubygems.org. Rails 7.2 needs Ruby 3.1.0 or newer. Both Ruby 3.1 and 3.2 have reached end of life; see Ruby end of life.
Who provides Rails support after end of life?
The Rails team does not publish releases for unsupported series. OSSeva patches Rails 8.0 and 7.2 after end of life and assesses other versions case by case through a version coverage check. Upgrading to Rails 8.1 is the other route.
What is the latest Ruby on Rails version?
8.1.4.1, released 3 Nov 2026, on the 8.1 line.
When is the next Ruby on Rails end of life?
Ruby on Rails 8.1 reaches the end of security support on 10 Oct 2027. After that date the project stops shipping security fixes for 8.1, and CVEs disclosed later stay unpatched upstream.
Which Ruby on Rails versions are still supported?
8.1 (until 10 Oct 2027). Every other line has reached end of life, per the dates in the table above.
Can I get security patches for an end-of-life Ruby on Rails version?
Yes. OSSeva ships signed builds with backported CVE fixes for Ruby on Rails 8.0 and 7.2 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.
Who provides Ruby on Rails support after end of life?
OSSeva provides Ruby on Rails extended support: patched, signed builds for Ruby on Rails 8.0 and 7.2 after upstream support ends, plus 24/7 operations on the Operate tier.
Get a quote
Still running an end-of-life Ruby on Rails?
Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.
Prefer to talk or read more first?