JRuby 9.3 · Version Status
JRuby 9.3 End of Life Date
JRuby 9.3 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
JRuby 9.3 is past end of life. This version no longer receives security patches. 783 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 26, 2024
783 days past EOL
Latest Release
9.3.15.0
Standard release
Release Date
Sep 22, 2021
JRuby 9.3 series
Lifecycle detail
JRuby 9.3 was released on September 22, 2021 and support ended on June 26, 2024 — a supported lifespan of 2 years and 9 months, in line with the 2 years and 9 months median for JRuby releases. It was not an LTS release; JRuby reserves longer patch windows for its LTS versions. The last patch it will ever receive is 9.3.15.0, published June 26, 2024 — on the day support ended. It has been without security patches for 2 years and 2 months. 2 newer JRuby releases have shipped since.
Attack Surface
10/30 Medium 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 JRuby 9.3 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| 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.15.0 |
EOL |
Active |
| 10.0 LTS |
10.0.6.0 |
Apr 1, 2028 |
Active |
| 10.1 |
10.1.1.0 |
EOL |
Active |
What does JRuby 9.3 end of life mean?
When JRuby 9.3 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.3 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.3 reach end of life?
JRuby 9.3 reached end of life on June 26, 2024. This version is no longer receiving security patches.
Is JRuby 9.3 still supported?
No. JRuby 9.3 reached end of life on June 26, 2024 and is no longer receiving security patches.
What should I upgrade to from JRuby 9.3?
The recommended upgrade from JRuby 9.3 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.3 past EOL?
When JRuby 9.3 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.