JRuby end of life dates
The support dates the endoflife.date record (community-maintained) holds for JRuby, read on 28 Oct 2026: when security support ends for each version (cycle), when active support ends, and extended support where the record shows it. Below them, what Cyber Essentials, the Essential Eight, CIS Controls v8, PCI DSS and NIST SP 800-53 ask of a version past its end.
Which JRuby versions are no longer supported?
On 28 Oct 2026, 4 of the 7 JRuby versions in the endoflife.date record are past vendor security support, the most recent being JRuby 9.3, JRuby 9.2 and JRuby 9.1. 3 are still supported, the newest being JRuby 10.1, JRuby 10.0 and JRuby 9.4.
How long will current JRuby versions be supported?
The next to lose security support is JRuby 10.0, on 1 Apr 2028. 2 have no end date announced, including JRuby 10.1 and JRuby 9.4. Dates from the endoflife.date record, read 28 Oct 2026; the vendor notice is authoritative.
How many JRuby versions are there?
The endoflife.date record holds 7 JRuby versions, from JRuby 9.0, released 21 Jul 2015, to JRuby 10.1, released 21 Apr 2026, read 28 Oct 2026.
Last updated: 2026-10-28. Every date on this page is the record's own, read 28 Oct 2026.
- Oldest version still in support
- 9.4, security support to no end date announced
- Next end date
- 10.0, security support ends 1 Apr 2028
- Editions and channels
- LTS marks a long-term support version, with longer dates than the standard versions beside it.
- Vendor's own notice
- the vendor lifecycle policy for JRuby, authoritative; each version below links its own notice where the record carries one
- Record
- JRuby
- Kind
- language runtime
- Versions in the record
- 7
- Versions past vendor support
- 4
- Essential Eight class
- an application outside the priority classes: ISM-0304 asks for its removal at ML3 only; at ML1 and ML2 no Essential Eight clause here turns on it
- Source
- endoflife.date/jruby, community-maintained, MIT licence, read 28 Oct 2026; sources
JRuby versions and their support dates
as at 28 Oct 2026| Cycle | Released | Active support ends | Security support ends | Extended support ends | On the read date | Vendor notice | |
|---|---|---|---|---|---|---|---|
| 10.1 | 21 Apr 2026 | not given separately | no end date announced | none in the record | supported, no end date announced | none in the record | |
| 10.0 LTS | 14 Apr 2025 | not given separately | 1 Apr 2028 | none in the record | supported | none in the record | |
| 9.4 | 23 Nov 2022 | not given separately | no end date announced | none in the record | supported, no end date announced | none in the record | |
| 9.3 | 22 Sep 2021 | not given separately | 26 Jun 2024 | none in the record | past vendor support | none in the record | |
| 9.2 | 24 May 2018 | not given separately | 27 Jun 2022 | none in the record | past vendor support | none in the record | |
| 9.1 | 2 May 2016 | not given separately | 20 Apr 2018 | none in the record | past vendor support | none in the record | |
| 9.0 | 21 Jul 2015 | not given separately | 30 Jan 2016 | none in the record | past vendor support | none in the record |
A version this table does not list is not in the record: the finder reads it as unknown, never supported. The dates are the record's own; nothing here states a date the record does not hold.
What the schemes ask of a version past its end
- Cyber Essentials
- software on in-scope devices licensed and supported by the vendor, meaning it still receives security updates; unsupported software removed or segregated (SU.1, SU.4). Cyber Essentials Plus: removed, or isolated with compensating controls (PM-02).
- Essential Eight
- An application outside the priority classes: ISM-0304 asks for its removal at ML3 only; at ML1 and ML2 no Essential Eight clause here turns on it
- CIS Controls v8, Safeguard 2.2
- only software that still receives vendor support may be marked authorised; unsupported software kept for the mission needs a recorded exception with compensating controls and the acceptance of the remaining risk; support status checked at least monthly.
- PCI DSS 12.3.4
- hardware and software reviewed at least every 12 months: that vendors still supply timely security fixes, end-of-life announcements documented, and a remediation plan for outdated technology approved by senior management.
- NIST SP 800-53 SA-22
- system components replaced when support is no longer available from the developer, vendor or manufacturer, or alternative sources of continued support provided.
- Cyber Essentials SU.1
- Cyber Essentials SU.4
- Cyber Essentials Plus PM-02
- CIS Controls v8 2.2
- PCI DSS 4.0 12.3.4
- NIST SP 800-53 SA-22
- ISO/IEC 27001 A.8.8
- ISO/IEC 27001 A.8.19
- Essential Eight Patch applications ISM-0304
See the specimen list runCheck your own list
Is my JRuby version still supported?
One line per version in the record, newest first, on 28 Oct 2026. Link to a line with its own address.
- Is JRuby 10.1 still supported? Yes: security support, no end date announced.
- Is JRuby 10.0 still supported? Yes: security support to 1 Apr 2028.
- Is JRuby 9.4 still supported? Yes: security support, no end date announced.
- Is JRuby 9.3 still supported? No. Security support for JRuby 9.3 ended 26 Jun 2024.
- Is JRuby 9.2 still supported? No. Security support for JRuby 9.2 ended 27 Jun 2022.
- Is JRuby 9.1 still supported? No. Security support for JRuby 9.1 ended 20 Apr 2018.
- Is JRuby 9.0 still supported? No. Security support for JRuby 9.0 ended 30 Jan 2016.