WILDFLY AND JBOSS COVERAGE

WildFly fixes security issues only in its newest release. Your server may not be on it.

WildFly, the open-source JBoss application server, has no end-of-life dates: the project fixes security issues only in its most recent release, and a new release ships about every three months. WildFly 42 shipped on 22 October 2026. OSSeva patches WildFly releases once a newer one has superseded them, starting with WildFly 41. It does not patch Red Hat JBoss EAP.

Who it is forTeams running community WildFly or old JBoss AS in production that cannot upgrade the server every quarter
What you getSigned patched builds on the WildFly release you run, with deployments, configuration and Java version unchanged. Assure adds an inventory and an upgrade or EAP-versus-WildFly assessment.
What it does not coverRed Hat JBoss EAP binaries and Red Hat subscriptions. EAP customers get support from Red Hat.
How it is pricedPer application. Ask for a quote.
What happens nextYou send your work email, we confirm your server version and whether it is WildFly, JBoss AS or EAP, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Last reviewed

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

WildFly releases and Red Hat EAP 7 status, read on 19 November 2026

WildFly has no support calendar, so the table shows when each release shipped and when the next one superseded it. The WildFly project's security policy says fixes go only into the most recent minor release.

ReleaseFirst final releaseSuperseded byProject fixes it?
WildFly 4222 Oct 2026CurrentYes, as the newest release
WildFly 4116 Jul 2026 (41.0.1 on 26 Aug 2026)42 on 22 Oct 2026No
WildFly 4021 May 2026 (40.0.1 on 22 Jun 2026)41 on 16 Jul 2026No
WildFly 3916 Jan 2026 (39.0.1 on 12 Feb 2026)40 on 21 May 2026No
WildFly 3816 Oct 2025 (38.0.1 on 17 Nov 2025)39 on 16 Jan 2026No
Red Hat JBoss EAP 7Red Hat productMaintenance support ended 30 Jun 2025Red Hat, under subscription

Release dates are the WildFly GitHub release timestamps (UTC). The Red Hat row is from Red Hat's JBoss EAP life cycle page and endoflife.date, which both give 30 June 2025 for the end of EAP 7 maintenance support. endoflife.date has no WildFly product.

WildFly security policy →WildFly news and release announcements →WildFly releases on GitHub →Red Hat JBoss EAP life cycle →endoflife.date JBoss EAP data →

WildFly, JBoss AS and JBoss EAP: which one are you running

The word JBoss covers three things with different owners. Which one you run decides who patches it.

  • WildFly is the open-source application server from the WildFly community. It has no support period, and the project fixes security issues only in the newest release. This is what OSSeva patches.
  • JBoss AS is the earlier name of the same project. The server was renamed WildFly with release 8, so a JBoss AS 7 or older installation is a pre-WildFly build that no one upstream fixes. OSSeva assesses these case by case.
  • Red Hat JBoss Enterprise Application Platform (EAP) is Red Hat's commercial product. EAP 7 maintenance support ended on 30 June 2025 and extended life cycle support is sold separately. EAP customers get support from Red Hat under their subscription. OSSeva does not patch or replace EAP binaries or subscriptions.
  • How to tell them apart: an EAP install has a Red Hat subscription behind it and an EAP version such as 7.4 in its release notes. A WildFly install is numbered 8 to 42 and downloaded from wildfly.org.
  • Moving from EAP to WildFly is a real migration, not a repackage. Test the application on the WildFly release you target before you drop a subscription.

Sources: the WildFly security policy and news page, and Red Hat's JBoss EAP life cycle page, read on 19 November 2026. The WildFly 8 rename is from the project's history.

Apache Tomcat support →Eclipse Jetty support →Hibernate ORM support →Java versions and end dates →

Why staying current on WildFly is harder than it sounds

A quarterly cadence with fixes only in the newest release means the policy asks you to upgrade the server four times a year. Whether that is realistic depends on what is deployed on it.

  • Each WildFly release moves the server, its specification implementations and bundled libraries, including the Hibernate version inside the server. An application tested on one release is retested on the next.
  • Applications that use server modules, custom subsystems or the old javax namespace take the longest. Check deployment descriptors, jboss-deployment-structure.xml and any module definitions before you plan an upgrade.
  • Embedded and bundled copies are common. Look for WildFly inside Docker images, Maven plugins and third-party products that ship a server in their install directory.
  • Patching first is reasonable when a validated application cannot be re-tested every quarter. OSSeva ships patched builds for the release you run, on your current Java version.
  • Moving to the newest WildFly stays the permanent fix. Patching covers the gap while you plan it.

Sources: the WildFly security policy and release history, read on 19 November 2026.

Spring Boot support →Apache Tomcat support →

Why now

The project's policy is the latest release only

The WildFly project's security policy says it takes immediate action on serious security problems and will only fix such issues in the most recent minor release of WildFly. WildFly publishes no support period for any release, so a release has no end-of-life date: it is superseded when the next one ships.

A new WildFly arrives about every three months

WildFly 42.0.0.Final shipped on 22 October 2026, three months after WildFly 41 (16 July 2026), which followed WildFly 40 (21 May 2026). The project describes a January, April, July and October schedule. Each release can change server, specification and library versions, so staying on the newest one is an upgrade project each quarter.

JBoss EAP 7 left Red Hat maintenance on 30 June 2025

Many applications described as JBoss are WildFly or old JBoss AS builds, and many are Red Hat JBoss EAP. Red Hat's life cycle page lists EAP 7 maintenance support to 30 June 2025 and sells extended life cycle support from 1 July 2025. EAP customers get support from Red Hat under their subscription.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
42(Released 22 Oct 2026. Newest, so the only release the project fixes)CurrentSee advisories
41(Released 16 Jul 2026. Superseded by 42 on 22 Oct 2026)EOLSee advisories
40 and earlier(Superseded. Assessed case by case.)EOLSee advisories
JBoss AS 7 and earlier(Renamed WildFly with release 8. Assessed case by case.)EOLSee advisories

Running a WildFly version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Security patches for WildFly releases the project no longer fixes.

  • Backported security fixes for WildFly 41 and other superseded releases
  • Critical CVEs fixed within 48 hours, High within 7 days
  • Signed artifacts (GPG + Sigstore)
  • CVE disclosure notifications
  • Architecture review
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus compliance documentation and an upgrade or EAP-versus-WildFly assessment.

  • Everything in Patch
  • Inventory of WildFly, JBoss AS and EAP servers and which one each application runs on
  • Upgrade path assessment to the current WildFly release
  • SOC 2 / HIPAA attestation package
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.

  • Everything in Assure
  • 24/7 application server monitoring
  • 15-minute P1 incident response SLA
  • Named senior engineer on your account

All tiers priced per cluster/application — not per core.

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

Is WildFly end of life?

WildFly has no fixed end-of-life calendar. The project's security policy says it will only fix security issues in the most recent minor release, and a new WildFly ships about every three months, so any release except the newest is effectively unfixed by the project. The newest is WildFly 42.0.0.Final, from 22 October 2026.

Is JBoss end of life?

It depends which JBoss. JBoss AS was renamed WildFly with release 8. Red Hat JBoss EAP 7 left Red Hat maintenance support on 30 June 2025, and Red Hat sells extended life cycle support from 1 July 2025. EAP 8 is a separate, later line.

What is the difference between WildFly and JBoss EAP?

WildFly is the open-source community application server. JBoss Enterprise Application Platform is Red Hat's commercial product, sold under subscription with Red Hat support. OSSeva supports WildFly and JBoss AS deployments. It does not patch or replace EAP binaries or Red Hat subscriptions.

Which WildFly versions does OSSeva patch?

WildFly releases once a newer one has superseded them, starting with WildFly 41, which WildFly 42 superseded on 22 October 2026. Other versions, including older WildFly and JBoss AS 7, are assessed case by case through a version coverage check.

Who provides WildFly support after a release is superseded?

The WildFly project fixes security issues only in its most recent minor release. Red Hat supports JBoss EAP, its commercial product, under subscription. For community WildFly and JBoss AS deployments, third-party providers such as OSSeva patch the older releases. Ask each which versions it covers.

How often is WildFly released?

About every three months. WildFly 40 shipped on 21 May 2026, 41 on 16 July 2026 and 42 on 22 October 2026, per the project's GitHub releases. The project describes a January, April, July and October schedule.

Can I keep running JBoss EAP 7 after June 2025?

That is a decision for your Red Hat subscription. Red Hat lists EAP 7 maintenance support to 30 June 2025 and says extended life cycle support should be purchased before it starts on 1 July 2025. OSSeva does not provide Red Hat EAP binaries or subscriptions. If the application can run on WildFly, OSSeva can patch that.

How is OSSeva WildFly support priced?

It is priced per application. Request a quote and a senior engineer replies within 1 business day.

Get a quote

Ready to get WildFly patched and supported?

Tell us your WildFly versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call