WildFly End of Life - Dates and Lifecycle
WildFly is a free, open-source Java application server developed by Red Hat and the WildFly community, implementing the Jakarta EE specification for building and deploying enterprise Java applications.
Last updated 24 July 2026
9
Versions tracked
8
At EOL
1
Supported
All versions
| Version | Released | Security Support | Latest |
|---|---|---|---|
|
41
|
16 Jul 2026 | — | — |
|
40.0.1
|
19 Jun 2026 |
16 Jul 2026
Ended 1 week, 1 day ago
|
— |
|
40
|
21 May 2026 |
19 Jun 2026
Ended 1 month ago
|
— |
|
39
|
16 Jan 2026 |
21 May 2026
Ended 2 months ago
|
— |
|
34
|
17 Oct 2024 |
16 Jan 2026
Ended 6 months, 1 week ago
|
— |
|
33
|
23 Jul 2024 |
17 Oct 2024
Ended 1 year, 9 months ago
|
— |
|
30
|
18 Oct 2023 |
23 Jul 2024
Ended 2 years ago
|
— |
|
27
|
09 Nov 2022 |
18 Oct 2023
Ended 2 years, 9 months ago
|
— |
About WildFly
WildFly is a free, open-source Java application server developed by Red Hat and the WildFly community, implementing the Jakarta EE specification for building and running enterprise Java applications. It's the open-source upstream project that Red Hat's commercial JBoss EAP product is built from.
WildFly Lifecycle Explained
WildFly's release cycle works differently from most software covered on this site, and the WildFly team has stated their policy directly: "the WildFly project generally doesn't continue to produce bug-fix releases for older versions once a new major or minor release is out." In practice, a new major version ships roughly every quarter, typically aiming for a January, April, July, and October cadence, though releases sometimes slip by several weeks. Each major version usually gets exactly one bug-fix patch release about a month later, and once the next quarterly major version ships, that's it, no further patches, security fixes included.
The one notable exception in WildFly's history illustrates this policy well. In January 2023, roughly two months after WildFly 27 had already superseded WildFly 26, the project issued WildFly 26.1.3 specifically to backport a fix for a critical Apache CXF vulnerability. They explained they were making an exception because the migration to WildFly 27 and its Jakarta EE 10 support was taking users longer than usual, not because their standard policy had changed. Outside of situations like that, once a version is superseded, it stays superseded.
WildFly also ships a WildFly Preview distribution alongside the standard release, which gets newer or experimental Jakarta EE features before they're promoted into the standard distribution, and, starting around WildFly 40, a WildFly EE 10 distribution for users who want EE 10 support after the standard distribution has moved on to a newer EE version.
Frequently Asked Questions
How does WildFly's release lifecycle work?
WildFly ships a new major version roughly every quarter, and each one typically gets a single bug-fix patch about a month later. After that, and once the next quarterly release ships, the version receives no further updates by policy, there's no multi-year support window like an operating system or enterprise product would have.
Does WildFly backport security fixes to old versions?
Generally, no. The WildFly project has stated directly that it doesn't produce bug-fix releases for older versions once a newer one is out. The one documented exception was a critical Apache CXF CVE backported to WildFly 26 after it had already been superseded, explicitly framed by the team as a rare departure from their usual approach.
How often does WildFly release a new version?
Roughly every three months, aiming for a January, April, July, and October cadence, though the team has occasionally acknowledged slipping behind that schedule by several weeks for larger releases.
What is WildFly Preview?
WildFly Preview is a separate distribution that includes newer or experimental Jakarta EE features before they're stable enough for the standard WildFly distribution. It follows the same quarterly release and end of life pattern as standard WildFly.