EOL.WikiEOL.Wiki
← ← Back to all products

Bellsoft Liberica JDKEnd of Life (EOL) Dates & Support Status

Active
Runtimes & JDKsLatest Version: 27+36Latest Release: Sep 16, 2026

BellSoft Liberica JDK is an OpenJDK distribution optimized for cloud, server, and desktop deployments.

Support summary

Bellsoft Liberica JDK 8 reaches EOL in 64 days. Start upgrade planning and compatibility testing now.

What do EOL and support statuses mean?

Next EOL

Nov 30, 2026

Bellsoft Liberica JDK 8 · 64 days left

Supported cycles

5

7 lts

Versions

21

Latest Version

27+36

Active Support

5

EOL

16

Lifecycle Timeline

Mar 23, 2022As of Sep 27, 2026
27Active · Mar 23, 2027
26EOL · Sep 16, 2026
25Active · Sep 30, 2031
24EOL · Sep 16, 2025
23EOL · Mar 18, 2025
22EOL · Sep 17, 2024
21Active · Date not announced
20EOL · Sep 19, 2023
19EOL · Mar 21, 2023
18EOL · Sep 20, 2022
ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
27Sep 16, 2026MaintainedMar 23, 202727+36No
Active
26Mar 18, 2026EndedSep 16, 202626.0.2.1+1No
EOL
25Sep 16, 2025MaintainedSep 30, 203125.0.4.1+1
Yes
Active
24Mar 19, 2025EndedSep 16, 202524.0.2+12No
EOL
23Sep 18, 2024EndedMar 18, 202523.0.2+9No
EOL
22Mar 20, 2024EndedSep 17, 202422.0.2+11No
EOL
21Sep 20, 2023MaintainedDate not announced21.0.12.1+2
Yes
Active
20Mar 22, 2023EndedSep 19, 202320.0.2+10No
EOL
19Sep 21, 2022EndedMar 21, 202319.0.2+9No
EOL
18Mar 23, 2022EndedSep 20, 202218.0.2.1+1No
EOL
17Sep 17, 2021MaintainedOct 31, 202717.0.20.1+2
Yes
Active
16Mar 19, 2021EndedSep 14, 202116.0.2+7No
EOL
15Sep 17, 2020EndedMar 16, 202115.0.2+10No
EOL
14Mar 19, 2020EndedSep 16, 202014.0.2+13No
EOL
13Sep 26, 2019EndedMar 17, 202013.0.2+9No
EOL
12Mar 22, 2019EndedSep 17, 201912.0.2No
EOL
11Oct 8, 2018EndedOct 31, 202411.0.32.1+1
Yes
EOL
10Mar 21, 2018EndedSep 25, 201810.0.2No
EOL
8Mar 18, 2014MaintainedNov 30, 20268u504+1
Yes
Active
7Jul 11, 2011EndedJul 31, 2022unknown
Yes
EOL
6Dec 12, 2006EndedDec 31, 2018unknown
Yes
EOL

Data sources

Embed this badge

Bellsoft Liberica JDK end-of-life support status badge

Show Bellsoft Liberica JDK's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.

Markdown

[![Bellsoft Liberica JDK end-of-life status](https://eol.wiki/badge/bellsoft-liberica.svg)](https://eol.wiki/bellsoft-liberica/)

HTML

<a href="https://eol.wiki/bellsoft-liberica/"><img src="https://eol.wiki/badge/bellsoft-liberica.svg" alt="Bellsoft Liberica JDK end-of-life status" height="20"></a>
All badges & lifecycle API →

Frequently Asked Questions

Which versions of Bellsoft Liberica JDK have reached end of life?
The following Bellsoft Liberica JDK versions have reached end of life and no longer receive security updates: 26, 24, 23, 22, 20, 19, 18, 16 (and 8 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Bellsoft Liberica JDK 26?
Bellsoft Liberica JDK 26 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Bellsoft Liberica JDK?
The latest version of Bellsoft Liberica JDK is 27+36, released in the 27 release cycle.
How many versions of Bellsoft Liberica JDK are currently supported?
Bellsoft Liberica JDK currently has 5 actively supported version(s): 27, 25, 21, 17, 8.
When does Bellsoft Liberica JDK 27 reach end of life?
Bellsoft Liberica JDK 27 is scheduled to reach end of life on Mar 23, 2027.
What should I do when Bellsoft Liberica JDK reaches end of life?
When a Bellsoft Liberica JDK version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.