No. Ruby 4.0 is supported and gets security updates until 31 March 2029 (in 2.4 years).
- Released
- 25 December 2025
- Security support ends
- 31 March 2029
- Latest release
- 4.0.9 · 22 October 2026
- Long-term support
- No
What this means for your servers
Ruby 4.0 is safe to run. Install updates regularly so you stay on the latest release in this cycle (4.0.9). Put 31 March 2029 in your calendar and plan the upgrade six months ahead.
How to check if you’re running Ruby 4.0
CLI
ruby -vWhat to upgrade to
Ruby 4.0 is already the newest recommended release.
Each Ruby branch is maintained for about three years. Install the new version with a version manager (rbenv, asdf, chruby) or a ruby:<version> image, update .ruby-version, then run bundle install and your test suite.
Find end-of-life software before an auditor does
Statance reads the version from official Ruby container image tags on your servers and raises a security finding when it goes past end of life or falls behind the latest patch, along with known CVEs from OSV.dev and CISA’s Known Exploited Vulnerabilities list. Security monitoring is included in Pro and Business. How security monitoring works.
Other Ruby releases
| Release | Status | Security support ends |
|---|---|---|
| Ruby 3.4 | Supported | 31 March 2028 |
| Ruby 3.3 | Supported | 31 March 2027 |
| Ruby 3.2 | End of life | 31 March 2026 |
FAQ
Is Ruby 4.0 end of life?
No. Ruby 4.0 is supported and gets security updates until 31 March 2029 (in 2.4 years).
When does Ruby 4.0 reach end of life?
Security support for Ruby 4.0 ends on 31 March 2029.
Can I keep running Ruby 4.0 after end of life?
It keeps working, but new vulnerabilities will not be fixed, so every newly published CVE stays open on your server. Scanners and compliance frameworks (PCI DSS, SOC 2, Cyber Essentials) treat unsupported software as a finding.
What is the latest version of Ruby 4.0?
The latest release in this cycle is 4.0.9, released on 22 October 2026.
Lifecycle data from endoflife.date/ruby, refreshed 17 November 2026. Vendors occasionally change dates; check the vendor’s own lifecycle page before making a compliance decision.
Stop tracking end-of-life dates by hand.
Statance flags end-of-life and vulnerable software on every server automatically.