Ruby End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Ruby versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.9.3 | 1.9.3p551 | Oct 30, 2011 | Feb 23, 2015 | 4185 days past EOL | EOL |
| 2.0.0 | 2.0.0p648 | Feb 24, 2013 | Feb 24, 2016 | 3819 days past EOL | EOL |
| 2.1 | 2.1.10 | Dec 25, 2013 | Mar 31, 2017 | 3418 days past EOL | EOL |
| 2.2 | 2.2.10 | Dec 25, 2014 | Mar 31, 2018 | 3053 days past EOL | EOL |
| 2.3 | 2.3.8 | Dec 24, 2015 | Mar 31, 2019 | 2688 days past EOL | EOL |
| 2.4 | 2.4.10 | Dec 23, 2016 | Mar 31, 2020 | 2322 days past EOL | EOL |
| 2.5 | 2.5.9 | Dec 25, 2017 | Mar 31, 2021 | 1957 days past EOL | EOL |
| 2.6 | 2.6.10 | Dec 25, 2018 | Mar 31, 2022 | 1592 days past EOL | EOL |
| 2.7 | 2.7.8 | Dec 25, 2019 | Mar 31, 2023 | 1227 days past EOL | EOL |
| 3.0 | 3.0.7 | Dec 25, 2020 | Apr 23, 2024 | 838 days past EOL | EOL |
| 3.1 | 3.1.7 | Dec 25, 2021 | Mar 26, 2025 | 501 days past EOL | EOL |
| 3.2 | 3.2.11 | Dec 25, 2022 | Apr 1, 2026 | 130 days past EOL | EOL |
| 3.3 | 3.3.12 | Dec 25, 2023 | Mar 31, 2027 | 234 days remaining | Active |
| 3.4 | 3.4.10 | Dec 24, 2024 | Mar 31, 2028 | 600 days remaining | Active |
| 4.0 | 4.0.6 | Dec 25, 2025 | Mar 31, 2029 | 965 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/ruby)
What does Ruby end of life mean for your organization?
When a version of Ruby reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Ruby should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Ruby reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Ruby versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Ruby has 12 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Ruby exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.