Ruby 3.2 · Version Status
Ruby 3.2 End of Life Date
Ruby 3.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Ruby 3.2 is past end of life. This version no longer receives security patches. 104 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 31, 2026
104 days past EOL
Latest Release
3.2.11
Standard release
Release Date
Dec 25, 2022
Ruby 3.2 series
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 → ·
View score card →
Extended Support
Extended Ruby 3.2 support is available
Commercial vendors offer security patches beyond EOL — compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1.9.3 |
1.9.3p551 |
Feb 23, 2015 |
EOL |
| 2.0.0 |
2.0.0p648 |
Feb 24, 2016 |
EOL |
| 2.1 |
2.1.10 |
Mar 31, 2017 |
EOL |
| 2.2 |
2.2.10 |
Mar 31, 2018 |
EOL |
| 2.3 |
2.3.8 |
Mar 31, 2019 |
EOL |
| 2.4 |
2.4.10 |
Mar 31, 2020 |
EOL |
| 2.5 |
2.5.9 |
Mar 31, 2021 |
EOL |
| 2.6 |
2.6.10 |
Mar 31, 2022 |
EOL |
What does Ruby 3.2 end of life mean?
When Ruby 3.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Ruby 3.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Ruby 4.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Ruby 3.2 reach end of life?
Ruby 3.2 reached end of life on March 31, 2026. This version is no longer receiving security patches.
Is Ruby 3.2 still supported?
No. Ruby 3.2 reached end of life on March 31, 2026 and is no longer receiving security patches.
What should I upgrade to from Ruby 3.2?
The recommended upgrade from Ruby 3.2 is
Ruby 4.0 — the latest actively supported version. Check the
Ruby full timeline for all supported versions.
What are the security risks of running Ruby 3.2 past EOL?
When Ruby 3.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Ruby should migrate immediately or implement compensating controls.
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.