Ruby EOL: end-of-life dates for every Ruby version
Ruby 3.2 reached end of life on 1 April 2026, and its final release was 3.2.11 on 27 March 2026. Ruby 3.3 follows on 31 March 2027, while Ruby 3.4 and 4.0 are in normal maintenance. OSSeva patches Ruby 3.2 and 3.1 after end of life; other versions are assessed case by case. Dates checked against ruby-lang.org and endoflife.date on 19 November 2026.
- Latest release
- 4.0.10
- Supported lines
- 3
- End-of-life lines
- 13
- Next end of life
- 3.3 · 31 Mar 2027
Ruby 3.1 and 3.2 have ended; 3.3 is next
Upgrade, or keep Ruby 3.2 and 3.1 patched
Most applications should move to Ruby 3.4 or 4.0. When a gem, a Rails version or a deployment image holds a service on 3.1 or 3.2, OSSeva patches both. Other Ruby versions are assessed case by case. Critical fixes ship within 48 hours and High within 7 days.
Who patches Ruby after end of life
OSSeva provides Ruby extended support: patched, signed builds for Ruby 3.2 and 3.1 after upstream support ends, plus 24/7 operations on the Operate tier.
Ruby release timeline
All Ruby versions, release dates and end-of-life dates
| Version | Released | Support Status | Latest | OSSeva |
|---|---|---|---|---|
| 4.0 | 11 months ago(25 Dec 2025) | Ends in 2 years and 4 months(31 Mar 2029) | 4.0.10 | – |
| 3.4 | 1 year and 11 months ago(24 Dec 2024) | Ends in 1 year and 4 months(31 Mar 2028) | 3.4.13 | – |
| 3.3 | 2 years and 11 months ago(25 Dec 2023) | Ends in 4 months(31 Mar 2027) | 3.3.14 | – |
| 3.2 | 3 years and 11 months ago(25 Dec 2022) | Ended 8 months ago(1 Apr 2026) | 3.2.11 | Patched |
| 3.1 | 4 years and 11 months ago(25 Dec 2021) | Ended 1 year and 8 months ago(26 Mar 2025) | 3.1.7 | Patched |
| 3.0 | 5 years and 11 months ago(25 Dec 2020) | Ended 2 years and 7 months ago(23 Apr 2024) | 3.0.7 | – |
| 2.7 | 6 years and 11 months ago(25 Dec 2019) | Ended 3 years and 8 months ago(31 Mar 2023) | 2.7.8 | – |
| 2.6 | 7 years and 11 months ago(25 Dec 2018) | Ended 4 years and 8 months ago(31 Mar 2022) | 2.6.10 | – |
| 2.5 | 8 years and 11 months ago(25 Dec 2017) | Ended 5 years and 8 months ago(31 Mar 2021) | 2.5.9 | – |
| 2.4 | 9 years and 11 months ago(23 Dec 2016) | Ended 6 years and 8 months ago(31 Mar 2020) | 2.4.10 | – |
| 2.3 | 10 years and 11 months ago(24 Dec 2015) | Ended 7 years and 8 months ago(31 Mar 2019) | 2.3.8 | – |
| 2.2 | 11 years and 11 months ago(25 Dec 2014) | Ended 8 years and 8 months ago(31 Mar 2018) | 2.2.10 | – |
| 2.1 | 12 years and 11 months ago(25 Dec 2013) | Ended 9 years and 8 months ago(31 Mar 2017) | 2.1.10 | – |
| 2.0.0 | 13 years and 9 months ago(24 Feb 2013) | Ended 10 years and 9 months ago(24 Feb 2016) | 2.0.0p648 | – |
| 1.9.3 | 15 years and 1 month ago(30 Oct 2011) | Ended 11 years and 9 months ago(23 Feb 2015) | 1.9.3p551 | – |
| 1.8 | 23 years and 4 months ago(4 Aug 2003) | Ended 13 years and 5 months ago(30 Jun 2013) | 1.8.7p374 | – |
Lifecycle data from endoflife.date (MIT licence), refreshed 21 Nov 2026. Upstream policy: www.ruby-lang.org. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
Ruby 3.1, 3.2 and 3.3 end of life dates
Ruby 3.1 and 3.2 are past end of life, and 3.3 is next. The Ruby core team does not use an LTS label: each branch moves from normal maintenance (bug fixes and security fixes) to a second phase and then to end of life, when no further patch release is made (ruby-lang.org/en/downloads/branches). On 18 November 2026 the team renamed the second phase for Ruby 3.3 from security maintenance to legacy maintenance, because 3.3.14 now also takes bug fixes the team judges worth backporting. The support period is unchanged.
Ruby branch status and end of life. Source: ruby-lang.org/en/downloads/branches, read on 19 November 2026, and endoflife.date.
| Branch | Released | Status | End of life |
|---|---|---|---|
| Ruby 3.1 | 25 Dec 2021 | End of life | 26 Mar 2025 (last release 3.1.7) |
| Ruby 3.2 | 25 Dec 2022 | End of life | 1 Apr 2026 (last release 3.2.11) |
| Ruby 3.3 | 25 Dec 2023 | Legacy maintenance | 31 Mar 2027 (expected) |
| Ruby 3.4 | 25 Dec 2024 | Normal maintenance | Not announced |
| Ruby 4.0 | 25 Dec 2025 | Normal maintenance | Not announced |
The Ruby team's branches page gives 3.2 an end date of 1 April 2026; endoflife.date lists 31 March 2026. This page uses the Ruby team's date. The same page marks the 3.3 date as expected.
What changed when Ruby 3.2 ended
Ruby 3.2.11, released on 27 March 2026, was announced as the last of its series. It included a zlib gem update addressing CVE-2026-27820, and the notice said the team would provide no further updates, security fixes included, and recommended Ruby 3.4 or 4.0.
Two security notices since then show what an ended branch misses. The resolv advisory of 27 August 2026 covers CVE-2026-80212 and CVE-2026-80213 and says no release is planned for the 0.2.x resolv line that Ruby 3.2 ships, because the series has ended; the workaround is installing resolv 0.7.2 as a gem. The advisory of 18 November 2026 covers seven vulnerabilities in the regular expression engine and in String case conversion. The Ruby team fixed them in 4.0.10, 3.4.13 and 3.3.14 and states that Ruby 3.2 and earlier are at end of life and will not get the fixes. It also says it knows of proofs of concept that reach remote code execution in some of them. At the time of writing these seven carried GitHub advisory identifiers, not CVE numbers.
The 23 October 2026 notice shows the same pattern for earlier bugs: Ruby 4.0.9, 3.4.12 and 3.3.13 fixed regular expression bugs that GitLab had turned into remote code execution on its servers, and 3.2 is not in that list of releases.
Upgrading from 3.2 is two steps if you go through 3.3 and 3.4. Ruby 3.3.0 deprecated calling `it` without arguments in a block that has no ordinary parameters, and made Regexp.new accept at most two arguments. Ruby 3.4.0 emits a deprecation warning when a string literal in a file without a frozen_string_literal comment is mutated, and no longer allows block passing or keyword arguments in an index expression. Each of those is a code change that a test suite has to surface before the move. Rails applications have a second constraint: Rails 8.0 needs Ruby 3.2.0 or newer and Rails 7.2 needs Ruby 3.1.0 or newer, so the framework and the interpreter usually move together.
Who patches Ruby after end of life?
OSSeva patches Ruby 3.2 and 3.1 after end of life, and assesses other versions case by case through a version coverage check. The Ruby core team issues no further changes to an ended branch. Critical fixes ship within 48 hours and High within 7 days, and pricing is per application runtime.
Running an end-of-life Ruby version?
OSSeva keeps end-of-life Ruby 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 extended supportIs Ruby 3.2 end of life?
Yes. Ruby 3.2 reached end of life on 1 April 2026 per the Ruby branches page, and its final release was 3.2.11 on 27 March 2026. The Ruby team issues no security fixes for it, including the fixes in its 18 November 2026 advisory.
Is Ruby 3.1 end of life?
Yes. Ruby 3.1 reached end of life on 26 March 2025, and 3.1.7 was its final release. The Ruby team makes no further releases on the branch.
When does Ruby 3.3 reach end of life?
The Ruby team lists 31 March 2027 as the expected date. Ruby 3.3 is in legacy maintenance, and the 3.3.14 release notice of 18 November 2026 says official support is still scheduled to end at the end of March 2027.
When do Ruby 3.4 and Ruby 4.0 reach end of life?
The Ruby team has not announced end dates for either. Both are in normal maintenance. The latest releases listed on 18 November 2026 are 3.4.13 and 4.0.10.
Does Ruby have an LTS version?
No. The Ruby core team does not label any branch as long-term support. Each branch gets normal maintenance and then a second phase of security fixes and selected bug fixes, with an end date announced by the team.
Who provides Ruby support after end of life?
The Ruby core team does not. OSSeva patches Ruby 3.2 and 3.1 after end of life and assesses other versions case by case through a version coverage check. Upgrading to Ruby 3.4 or 4.0 is the other route.
What is the latest Ruby version?
4.0.10, released 18 Nov 2026, on the 4.0 line. Other supported lines: 3.4 and 3.3.
When is the next Ruby end of life?
Ruby 3.3 reaches the end of support status on 31 Mar 2027. After that date the project stops shipping security fixes for 3.3, and CVEs disclosed later stay unpatched upstream.
Which Ruby versions are still supported?
4.0 (until 31 Mar 2029), 3.4 (until 31 Mar 2028) and 3.3 (until 31 Mar 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 version?
Yes. OSSeva ships signed builds with backported CVE fixes for Ruby 3.2 and 3.1 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.
Get a quote
Still running an end-of-life Ruby?
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?