BellSoft Liberica 6 · Version Status
BellSoft Liberica 6 End of Life Date
BellSoft Liberica 6 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 6 is past end of life. Standard support ended December 31, 2018. Patches continue until March 31, 2028 only under BellSoft extended support, a paid programme — if you are not covered by it, this version is unpatched today.
EOL Date
Dec 31, 2018
2823 days past EOL
Latest Release
unknown
LTS release
Release Date
Dec 12, 2006
BellSoft Liberica 6 series
Extended Support
Mar 31, 2028
BellSoft extended support · paid
Lifecycle detail
BellSoft Liberica 6 was released on December 12, 2006 and support ended on December 31, 2018 — a supported lifespan of 12 years and 1 month, in line with the 11 years and 1 month median for BellSoft Liberica LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. Standard support ended 7 years and 9 months ago. Security fixes now come only through extended support, published to March 31, 2028; without it this version is unpatched. 16 newer BellSoft Liberica 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 BellSoft Liberica 6 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All BellSoft Liberica Versions
| Version | Latest | EOL Date | Status |
|---|
| → 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 6 end of life mean?
When BellSoft Liberica 6 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 6 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 6 reach end of life?
BellSoft Liberica 6 reached end of life on December 31, 2018. This version is no longer receiving security patches.
Is BellSoft Liberica 6 still supported?
No. BellSoft Liberica 6 reached end of life on December 31, 2018 and is no longer receiving security patches.
What should I upgrade to from BellSoft Liberica 6?
The recommended upgrade from BellSoft Liberica 6 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 6 past EOL?
When BellSoft Liberica 6 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.