BellSoft Liberica 26 · Version Status

BellSoft Liberica 26 End of Life Date

BellSoft Liberica 26 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

BellSoft Liberica 26 is past end of life. This version no longer receives security patches. 7 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 16, 2026
7 days past EOL
Latest Release
26.0.2.1+1
Standard release
Release Date
Mar 18, 2026
BellSoft Liberica 26 series
Lifecycle detail

BellSoft Liberica 26 was released on March 18, 2026 and support ended on September 16, 2026 — a supported lifespan of 6 months, in line with the 6 months median for BellSoft Liberica releases. It was not an LTS release; BellSoft Liberica reserves longer patch windows for its LTS versions. The last patch it will ever receive is 26.0.2.1+1, published August 19, 2026 — 28 days before support ended. It has been without security patches for 7 days.

← BellSoft Liberica 25 All BellSoft Liberica versions BellSoft Liberica 27 →
35 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
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 →
Recommended upgrade path
BellSoft Liberica 27
Latest release: 27+36 · EOL: Mar 23, 2027
View full BellSoft Liberica timeline →
Extended Support
Extended BellSoft Liberica 26 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All BellSoft Liberica Versions
VersionLatestEOL DateStatus
6 LTS unknown Dec 31, 2018 EOL
7 LTS unknown Jul 31, 2022 EOL
8 LTS 8u504+1 Nov 30, 2026 Warning
10 10.0.2 Sep 25, 2018 EOL
11 LTS 11.0.32.1+1 Oct 31, 2024 EOL
12 12.0.2 Sep 17, 2019 EOL
13 13.0.2+9 Mar 17, 2020 EOL
14 14.0.2+13 Sep 16, 2020 EOL

What does BellSoft Liberica 26 end of life mean?

When BellSoft Liberica 26 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running BellSoft Liberica 26 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to BellSoft Liberica 27 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does BellSoft Liberica 26 reach end of life?
BellSoft Liberica 26 reached end of life on September 16, 2026. This version is no longer receiving security patches.
Is BellSoft Liberica 26 still supported?
No. BellSoft Liberica 26 reached end of life on September 16, 2026 and is no longer receiving security patches.
What should I upgrade to from BellSoft Liberica 26?
The recommended upgrade from BellSoft Liberica 26 is BellSoft Liberica 27 — the latest actively supported version. Check the BellSoft Liberica full timeline for all supported versions.
What are the security risks of running BellSoft Liberica 26 past EOL?
When BellSoft Liberica 26 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL BellSoft Liberica should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →