GHC 8.0 · Version Status

GHC 8.0 End of Life Date

GHC 8.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

⚠ GHC 8.0 is past end of life. This version no longer receives security patches. Past EOL — migrate to a supported version immediately.
EOL Date
date not published
Past EOL
Latest Release
8.0.2
Standard release
Release Date
May 17, 2016
GHC 8.0 series
Lifecycle detail

GHC 8.0 was released on May 17, 2016. It is not an LTS release; GHC reserves longer patch windows for its LTS versions. Its most recent patch is 8.0.2, published January 11, 2017.

All GHC versions GHC 8.2 →
45 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/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
GHC 9.14
Latest release: 9.14.1 · EOL: Supported
View full GHC timeline →
Extended Support
Extended GHC 8.0 support is available

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

Compare Options →
All GHC Versions
VersionLatestEOL DateStatus
→ 8.0 8.0.2 Supported EOL
8.2 8.2.2 Supported EOL
8.4 8.4.4 Supported EOL
8.6 8.6.5 Supported EOL
8.8 8.8.4 Supported EOL
8.10 8.10.7 Supported EOL
9.0 9.0.2 Supported EOL
9.2 9.2.8 Supported EOL

What does GHC 8.0 end of life mean?

When GHC 8.0 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 GHC 8.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to GHC 9.14 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does GHC 8.0 reach end of life?
GHC 8.0 has already reached end of life, though the vendor has not published an exact date.
Is GHC 8.0 still supported?
No. GHC 8.0 reached end of life on date not published and is no longer receiving security patches.
What should I upgrade to from GHC 8.0?
The recommended upgrade from GHC 8.0 is GHC 9.14 — the latest actively supported version. Check the GHC full timeline for all supported versions.
What are the security risks of running GHC 8.0 past EOL?
When GHC 8.0 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 GHC should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →