← ← Back to all products
Red Hat JBoss EAP
Active
Tools & Monitoring Latest Version: 8.0.11.0 Latest Release: Dec 4, 2025
Red Hat JBoss EAP is an enterprise application platform for building Java EE applications.
Versions
6
Latest Version
8.0.11.0
Active Support
1
EOL
5
Lifecycle Timeline
Today ↓
8
8
7
7
6
6
5
5
4.3
4.3
4.2
4.2
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 8 | Feb 5, 2024 | Feb 5, 2028 | Feb 5, 2031 | 8.0.11.0 | No | Active |
| 7 | May 1, 2016 | Dec 31, 2023 | Jun 30, 2025 | 7.4.23 | No | EOL |
| 6 | Jun 1, 2012 | Jun 30, 2016 | Jun 30, 2019 | 6.4.24 | No | EOL |
| 5 | Nov 1, 2009 | Nov 30, 2013 | Nov 30, 2016 | 5.2.0 | No | EOL |
| 4.3 | Jan 1, 2008 | Jan 31, 2011 | Jan 31, 2013 | 4.3.0 CP10 | No | EOL |
| 4.2 | Jun 1, 2007 | Jun 30, 2010 | Jun 30, 2012 | 4.2.0.CP09 | No | EOL |
Frequently Asked Questions
Which versions of Red Hat JBoss EAP have reached end of life?
The following Red Hat JBoss EAP versions have reached end of life and no longer receive security updates: 7, 6, 5, 4.3, 4.2. It is recommended to upgrade to a supported version.
Is it safe to continue using Red Hat JBoss EAP 7?
Red Hat JBoss EAP 7 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 Red Hat JBoss EAP?
The latest version of Red Hat JBoss EAP is 8.0.11.0, released in the 8 release cycle.
How many versions of Red Hat JBoss EAP are currently supported?
Red Hat JBoss EAP currently has 1 actively supported version(s): 8.
When does Red Hat JBoss EAP 8 reach end of life?
Red Hat JBoss EAP 8 is scheduled to reach end of life on Feb 5, 2031.
What should I do when Red Hat JBoss EAP reaches end of life?
When a Red Hat JBoss EAP 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.