Complete end-of-life dates, support windows, and security status for all Jruby versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 9.0 | 9.0.5.0 | Jul 21, 2015 | Jan 30, 2016 | 3752 days past EOL | EOL |
| 9.1 | 9.1.17.0 | May 2, 2016 | Apr 20, 2018 | 2941 days past EOL | EOL |
| 9.2 | 9.2.21.0 | May 24, 2018 | Jun 27, 2022 | 1412 days past EOL | EOL |
| 9.3 | 9.3.15.0 | Sep 22, 2021 | Jun 26, 2024 | 682 days past EOL | EOL |
| 9.4 | 9.4.14.0 | Nov 23, 2022 | Already EOL | Supported | Active |
| 10.0 LTS | 10.0.5.0 | Apr 14, 2025 | Apr 1, 2028 | 693 days remaining | Active |
| 10.1 | 10.1.0.0 | Apr 21, 2026 | Already EOL | Supported | Active |
When a Jruby 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 Jruby 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 →