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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.9.3 | 1.9.3p551 | Oct 30, 2011 | Feb 23, 2015 | 4093 days past EOL | EOL |
| 2.0.0 | 2.0.0p648 | Feb 24, 2013 | Feb 24, 2016 | 3727 days past EOL | EOL |
| 2.1 | 2.1.10 | Dec 25, 2013 | Mar 31, 2017 | 3326 days past EOL | EOL |
| 2.2 | 2.2.10 | Dec 25, 2014 | Mar 31, 2018 | 2961 days past EOL | EOL |
| 2.3 | 2.3.8 | Dec 24, 2015 | Mar 31, 2019 | 2596 days past EOL | EOL |
| 2.4 | 2.4.10 | Dec 23, 2016 | Mar 31, 2020 | 2230 days past EOL | EOL |
| 2.5 | 2.5.9 | Dec 25, 2017 | Mar 31, 2021 | 1865 days past EOL | EOL |
| 2.6 | 2.6.10 | Dec 25, 2018 | Mar 31, 2022 | 1500 days past EOL | EOL |
| 2.7 | 2.7.8 | Dec 25, 2019 | Mar 31, 2023 | 1135 days past EOL | EOL |
| 3.0 | 3.0.7 | Dec 25, 2020 | Apr 23, 2024 | 746 days past EOL | EOL |
| 3.1 | 3.1.7 | Dec 25, 2021 | Mar 31, 2025 | 404 days past EOL | EOL |
| 3.2 | 3.2.11 | Dec 25, 2022 | Mar 31, 2026 | 39 days past EOL | EOL |
| 3.3 | 3.3.11 | Dec 25, 2023 | Mar 31, 2027 | 326 days remaining | Active |
| 3.4 | 3.4.9 | Dec 24, 2024 | Mar 31, 2028 | 692 days remaining | Active |
| 4.0 | 4.0.3 | Dec 25, 2025 | Mar 31, 2029 | 1057 days remaining | Active |
When a Ruby version 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →