Red Hat JBoss EAP 6 · Version Status
Red Hat JBoss EAP 6 End of Life Date
Red Hat JBoss EAP 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.
⚠
Red Hat JBoss EAP 6 is past end of life. Standard support ended June 30, 2019. Patches continue until December 30, 2028 only under Red Hat Extended Life Cycle Support, a paid programme — if you are not covered by it, this version is unpatched today.
EOL Date
Jun 30, 2019
2687 days past EOL
Latest Release
6.4.24
Standard release
Release Date
Jun 1, 2012
Red Hat JBoss EAP 6 series
Extended Support
Dec 30, 2028
Red Hat Extended Life Cycle Support · paid
Where these dates come from
End of lifeJun 30, 2019Vendor's own page, read by our adapter · access.redhat.com · checked Nov 3, 2026high · 2 sources agree End of active supportJun 30, 2016Vendor's own page, read by our adapter · access.redhat.com · checked Nov 3, 2026high · 2 sources agree End of extended supportDec 30, 2028Vendor's own page (our correction) · access.redhat.com · checked Sep 27, 2026medium · 1 source agrees ReleaseJun 1, 2012Vendor's own page, read by our adapter · access.redhat.com · checked Nov 3, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Red Hat JBoss EAP 6 was released on June 1, 2012 and support ended on June 30, 2019 — a supported lifespan of 7 years and 1 month, in line with the 7 years and 1 month median for Red Hat JBoss EAP releases. Its most recent release is 6.4.24, published June 30, 2022. Standard support ended 7 years and 4 months ago. Security fixes now come only through extended support, published to December 30, 2028; without it this version is unpatched. 1 newer Red Hat JBoss EAP release has shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA 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 Red Hat JBoss EAP 6 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All Red Hat JBoss EAP Versions
| Version | Latest | EOL Date | Status |
|---|
| 4.2 |
4.2.0.CP09 |
Jun 30, 2012 |
EOL |
| 4.3 |
4.3.0 CP10 |
Jan 31, 2013 |
EOL |
| 5 |
5.2.0 |
Nov 30, 2016 |
EOL |
| → 6 |
6.4.24 |
Jun 30, 2019 |
EOL |
| 7 |
7.4.25 |
Jun 30, 2025 |
EOL |
| 8 |
8.1.9 |
Feb 5, 2031 |
Active |
What does Red Hat JBoss EAP 6 end of life mean?
When Red Hat JBoss EAP 6 reaches end of life, the maintainers stop issuing security patches for this version except under Red Hat Extended Life Cycle Support (paid), until Dec 30, 2028. 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 Red Hat JBoss EAP 6 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Red Hat JBoss EAP 8 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Red Hat JBoss EAP 6 reach end of life?
Red Hat JBoss EAP 6 reached end of life on June 30, 2019. Security patches continue only under Red Hat Extended Life Cycle Support (paid), until December 30, 2028; without it this version receives none.
Is Red Hat JBoss EAP 6 still supported?
Not in standard support. Red Hat JBoss EAP 6 reached end of life on June 30, 2019; security patches continue only under Red Hat Extended Life Cycle Support (paid) until December 30, 2028.
What should I upgrade to from Red Hat JBoss EAP 6?
The recommended upgrade from Red Hat JBoss EAP 6 is
Red Hat JBoss EAP 8 — the latest actively supported version. Check the
Red Hat JBoss EAP full timeline for all supported versions.
What are the security risks of running Red Hat JBoss EAP 6 past EOL?
Since Red Hat JBoss EAP 6 reached end of life, the maintainers no longer issue security patches outside Red Hat Extended Life Cycle Support. 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 Red Hat JBoss EAP should migrate immediately or implement compensating controls.