RUBY COVERAGE
Ruby 3.2 and 3.1 are end of life. Your patching does not have to be.
Ruby extended support from OSSeva covers the interpreter versions the Ruby core team no longer fixes. Ruby 3.2 ended on 1 April 2026 and Ruby 3.1 on 26 March 2025, and the Ruby team's 18 November 2026 advisory says 3.2 and earlier will not receive its fixes. Send your work email and an engineer replies within 1 business day with coverage for your Ruby version.
| Who it is for | Teams running Ruby 3.1 or 3.2, often under Rails, Sidekiq or a deployment image they cannot rebuild on a new interpreter yet |
|---|---|
| What you get | Signed patched Ruby builds on your line, with syntax, gem compatibility and the C extension ABI unchanged. Assure adds an exposure audit, an upgrade path assessment and 24/7 reactive support. |
| How it is priced | Per application runtime. Ask for a quote. |
| What happens next | You send your work email, we confirm your Ruby version and how it is deployed, and you get a coverage plan. |
Reply within 1 business day · No commitment · or book a 15-minute call
Last reviewed
Trusted globally by enterprises





Ruby end-of-life dates, read on 19 November 2026
Dates are from the Ruby core team's branches page. Release dates and final releases are from the Ruby release announcements and endoflife.date.
| Branch | Status on ruby-lang.org | End of life | Final or latest release |
|---|---|---|---|
| 3.1 | eol | 26 Mar 2025 | 3.1.7 (26 Mar 2025) |
| 3.2 | eol | 1 Apr 2026 | 3.2.11 (27 Mar 2026), final release |
| 3.3 | legacy maintenance | 31 Mar 2027 (expected) | 3.3.14 (18 Nov 2026) |
| 3.4 | normal maintenance | TBD | 3.4.13 (18 Nov 2026) |
| 4.0 | normal maintenance | TBD | 4.0.10 (18 Nov 2026) |
The Ruby branches page gives 3.2 an end date of 2026-04-01; endoflife.date lists 2026-03-31. This page uses the Ruby team's date.
Ruby end-of-life dates for every branch →ruby-lang.org: Ruby branches →
Two resolv CVEs that Ruby 3.2 will not get fixed upstream
CVE-2026-80212 and CVE-2026-80213 are in the resolv gem that ships with Ruby. Both the CVE records and the Ruby advisory of 27 August 2026 list it as affected up to 0.7.1, and the advisory says no release is planned for the 0.2.x line that the Ruby 3.2 series ships.
| CVE | Issue | Severity on the CVE record | Fixed in |
|---|---|---|---|
| CVE-2026-80212 | Memory exhaustion through malicious DNS responses (resolv gem) | High, CVSS 7.5 | resolv 0.7.2, or 0.3.2 for Ruby 3.3. Not for Ruby 3.2: install resolv 0.7.2 |
| CVE-2026-80213 | Hostname validation bypass in the resolv DNS encoder | Medium, CVSS 4.0 | resolv 0.7.2, or 0.3.2 for Ruby 3.3. Not for Ruby 3.2: install resolv 0.7.2 |
Sources: cveawg.mitre.org/api/cve/CVE-2026-80212 and CVE-2026-80213, and the Ruby security notice of 27 August 2026. The seven Regexp and String advisories of 18 November 2026 had no CVE identifiers when this page was written, so they are not listed here.
Why now
Ruby 3.2 reached end of life on 1 April 2026
The ruby-lang.org branches page lists Ruby 3.2 as eol with an end date of 2026-04-01. The final release, 3.2.11 of 27 March 2026, was announced as the last of the series, with no further updates of any kind, security fixes included.
The 18 November 2026 Ruby advisory excludes 3.2
Ruby 4.0.10, 3.4.13 and 3.3.14 fix seven vulnerabilities in the regular expression engine and string case conversion, and the advisory states that Ruby 3.2 and earlier have reached end of life and will not get them. The Ruby team says it knows of proofs of concept that reach remote code execution in some of them.
Ruby 3.3 is the next line to leave
Ruby 3.3 is in legacy maintenance, and official support is still scheduled to end at the end of March 2027, per the Ruby 3.3.14 release notice. A team that moves from 3.2 to 3.3 faces the same decision within five months.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 3.1(Community EOL 26 Mar 2025 (last release 3.1.7)) | EOL | Clean |
| 3.2(Community EOL 1 Apr 2026 (last release 3.2.11)) | EOL | Clean |
| 3.3(Legacy maintenance; community EOL 31 Mar 2027. Assessed case by case.) | Current | Clean |
Running a Ruby version or build not listed here?
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Security patches for Ruby 3.2 and 3.1 after end of life.
- Backported security fixes for Ruby 3.2 and 3.1
- Critical CVEs fixed within 48 hours, High within 7 days
- Signed artifacts (GPG + Sigstore)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus compliance documentation and upgrade planning.
- Everything in Patch
- SOC 2 / HIPAA attestation package
- Ruby upgrade path assessment
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.
- Everything in Assure
- 24/7 application and runtime monitoring
- 15-minute P1 incident response SLA
- Named senior engineer on your account
All tiers priced per cluster/application — not per core.
Which Ruby versions does OSSeva patch?
Ruby 3.2 and 3.1 after end of life. Other versions are assessed case by case through a version coverage check.
How fast are Ruby vulnerabilities patched?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.
Does patching Ruby also patch Ruby on Rails?
No. Ruby on Rails is a separate gem with its own end-of-life dates, covered on the Ruby on Rails page. A Rails application on Ruby 3.2 can need both: the interpreter and the framework are patched independently.
How is OSSeva Ruby support priced?
It is priced per application runtime. Request a quote and a senior engineer replies within 1 business day.
Get a quote
Ready to get Ruby patched and supported?
Tell us your Ruby versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?