Ruby · Lifecycle Status

Ruby End of Life (EOL) Dates & Support Timeline

Q: What is the end-of-life date for Ruby?

The next Ruby version reaching EOL is 3.3 on March 31, 2027. See the full table above for all version EOL dates.

Q: When is the Ruby support end date?

The next Ruby support end date is March 31, 2027, when version 3.3 reaches end of support. Each version has its own support end date — see the table above for every version's date.

Q: What is the latest supported version of Ruby?

The latest active version of Ruby is 4.0.5. Always verify against the table above as support windows can change.

Q: Does Ruby track end-of-life by point release (e.g. Ruby 4.0.1, Ruby 4.0.2)?

No — Ruby end-of-life dates apply to the entire 4.0.x release series, not individual point releases. A point release like Ruby 4.0.1 or Ruby 4.0.2 shares the same EOL date as Ruby 4.0. Security patches stop for the entire 4.0.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.

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.

📅 Get reminded before Ruby 3.3 reaches EOL on March 31, 2027 — alerts 90, 30 & 7 days out.

Google →

Latest Active

4.0.5

4.0 series

Next EOL

3.3

Mar 31, 2027

Active Versions

of 15 total

EOL Versions

no longer patched

High Risk

EOL Risk Score™ How is this calculated? →

EOL Recency

25/40

Attack Surface

30/30 Critical tier

CISA KEV Exposure

0/20 Not in KEV

Extended Support

0/10 Available

EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →

Release Cycle Timeline

■ EOL ■ Warning ■ Active ┊ Today

All Versions

Version	Latest Release	Release Date	EOL Date	Days	Status
1.9.3	1.9.3p551	Oct 30, 2011	Feb 23, 2015	4138 days past EOL	EOL
2.0.0	2.0.0p648	Feb 24, 2013	Feb 24, 2016	3772 days past EOL	EOL
2.1	2.1.10	Dec 25, 2013	Mar 31, 2017	3371 days past EOL	EOL
2.2	2.2.10	Dec 25, 2014	Mar 31, 2018	3006 days past EOL	EOL
2.3	2.3.8	Dec 24, 2015	Mar 31, 2019	2641 days past EOL	EOL
2.4	2.4.10	Dec 23, 2016	Mar 31, 2020	2275 days past EOL	EOL
2.5	2.5.9	Dec 25, 2017	Mar 31, 2021	1910 days past EOL	EOL
2.6	2.6.10	Dec 25, 2018	Mar 31, 2022	1545 days past EOL	EOL
2.7	2.7.8	Dec 25, 2019	Mar 31, 2023	1180 days past EOL	EOL
3.0	3.0.7	Dec 25, 2020	Apr 23, 2024	791 days past EOL	EOL
3.1	3.1.7	Dec 25, 2021	Mar 31, 2025	449 days past EOL	EOL
3.2	3.2.11	Dec 25, 2022	Mar 31, 2026	84 days past EOL	EOL
3.3	3.3.11	Dec 25, 2023	Mar 31, 2027	281 days remaining	Active
3.4	3.4.9	Dec 24, 2024	Mar 31, 2028	647 days remaining	Active
4.0	4.0.5	Dec 25, 2025	Mar 31, 2029	1012 days remaining	Active

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.

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.

endoflife.ai

Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Frequently Asked Questions

What is the end-of-life date for Ruby?

The next Ruby version reaching EOL is 3.3 on March 31, 2027. See the full table above for all version EOL dates.

When is the Ruby support end date?

The next Ruby support end date is March 31, 2027, when version 3.3 reaches end of support. Each version has its own support end date — see the table above for every version's date.

What is the latest supported version of Ruby?

The latest active version of Ruby is 4.0.5. Always verify against the table above as support windows can change.

What happens when Ruby reaches end of life?

When Ruby reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.

How do I check if I'm running an EOL version of Ruby?

Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.

Is there extended support available for EOL Ruby versions?

Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Does Ruby track end-of-life by point release (e.g. Ruby 4.0.1, Ruby 4.0.2)?

No — Ruby end-of-life dates apply to the entire 4.0.x release series, not individual point releases. A point release like Ruby 4.0.1 or Ruby 4.0.2 shares the same EOL date as Ruby 4.0. Security patches stop for the entire 4.0.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →