Jruby 9.1 · Version Status
Jruby 9.1 End of Life Date
Jruby 9.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Jruby 9.1 is past end of life. This version no longer receives security patches. 2941 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 20, 2018
2941 days past EOL
Latest Release
9.1.17.0
Standard release
Release Date
May 2, 2016
Jruby 9.1 series
| Version | Latest | EOL Date | Status |
|---|
| 9.0 |
9.0.5.0 |
Jan 30, 2016 |
EOL |
| → 9.1 |
9.1.17.0 |
Apr 20, 2018 |
EOL |
| 9.2 |
9.2.21.0 |
Jun 27, 2022 |
EOL |
| 9.3 |
9.3.15.0 |
Jun 26, 2024 |
EOL |
| 9.4 |
9.4.14.0 |
EOL |
Active |
| 10.0 LTS |
10.0.5.0 |
Apr 1, 2028 |
Active |
| 10.1 |
10.1.0.0 |
EOL |
Active |
What does Jruby 9.1 end of life mean?
When Jruby 9.1 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 Jruby 9.1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Jruby 10.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Jruby 9.1 reach end of life?
Jruby 9.1 reached end of life on April 20, 2018. This version is no longer receiving security patches.
Is Jruby 9.1 still supported?
No. Jruby 9.1 reached end of life on April 20, 2018 and is no longer receiving security patches.
What should I upgrade to from Jruby 9.1?
The recommended upgrade from Jruby 9.1 is
Jruby 10.1 — the latest actively supported version. Check the
Jruby full timeline for all supported versions.
What are the security risks of running Jruby 9.1 past EOL?
When Jruby 9.1 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 Jruby should migrate immediately or implement compensating controls.