The November 2026 Azul Payara release patches security issues across every supported branch, from Azul Payara 7.6.0 down to Payara 4, including remote code execution in JMX, a remote admin authentication bypass, and the removal of the vulnerable eMudhra certificates from the Payara trust store. That last fix does not clean domains you have already upgraded, so they need a manual step. Payara Community 7.2026.11 ships the same fixes.
In this post you will learn:
- Which security fixes landed on which Azul Payara branches
- What the eMudhra trust store fix does, and what it does not do
- Why the 6, 5, and 4 lines carry an extra Hazelcast fix
- What else changes on each Azul Payara branch
- What Payara Community 7.2026.11 adds
If you run Azul Payara (request free trial here), this month’s main reason to upgrade is security. Five fixes ship across Azul Payara Server and Micro 7.6.0, 6.44.0, 5.93.0, and 4.1.2.191.61: remote code execution in JMX, a remote admin authentication bypass, a Jackson CVE, a Hazelcast jackson-core vulnerability, and the removal of vulnerable certificate authorities from the Payara trust store. The 6, 5, and 4 lines carry a sixth, a Hazelcast backport for two CVEs.
The release notes list no breaking changes this cycle, and by the end of this post you will know which items apply to the line you run.
Security Fixes Across Every Branch
Remote code execution in JMX (CVE-2026-90908), a remote admin authentication bypass (CVE-2026-110003), CVE-2026-110879 (Jackson updated to 2.22.4 / 2.21.8 / 2.18.12), a Hazelcast jackson-core vulnerability (GHSA-r7wm-3cxj-wff9), and the vulnerable eMudhra certificates (CVE-2026-91403 and CVE-2026-114820) are fixed on every supported Azul Payara branch. Azul Payara 6.44.0, 5.93.0, and 4.1.2.191.61 also carry a Hazelcast backport for CVE-2026-107725 and CVE-2026-107726; Payara 7 is not affected by those two. Azul is a registered CVE Numbering Authority under CISA and DHS oversight, and patches are backported to every supported version on a published monthly schedule. There is no reason to delay upgrading based on the major-version line you run. The Azul Payara Security Advisories page has the details.
The eMudhra Trust Store Fix, and What It Does Not Do
Every release this month removes the four vulnerable certificates from Payara’s default trust store. The change only applies to new installations and to domains created with the fixed releases. An in-place upgrade does not normally update the trust store, so on an upgraded domain you must remove the certificates manually, and update to a JDK that contains the fix. The Azul Payara Security Advisories page lists the fingerprints of the certificates to remove.
What’s New in Azul Payara Server and Micro 7.6.0
Azul Payara Server and Micro 7.6.0 is the sixth monthly release since Payara 7 reached general availability in May. Server 7.6.0 is Jakarta EE 11 certified across Full Platform, Web Profile, and Core Profile, on MicroProfile 7.1.
Beyond security, 7.6.0 fixes context capture for managed executors throwing an IllegalStateException on threads with no component invocation, the start-domain admin-password recovery prompt, an EclipseLink multithreading issue, and a deadlock in the EclipseLink second-level cache. The OpenMQ examples and Javadoc and the H2 database source files and help docs are no longer bundled. Mojarra moves to 4.1.18 and the Jackson BOM to 2.22.4.
The 6, 5, and 4 Lines
Azul Payara Server and Micro 6.44.0 continues the Jakarta EE 10 line on MicroProfile 7.1, with the managed executor fix, the two EclipseLink fixes, and Mojarra 4.0.27. Azul Payara Server and Micro 5.93.0 stays on Jakarta EE 8 and MicroProfile 4.1, with the two EclipseLink fixes and jakarta.mail 1.6.8. Both no longer bundle the OpenMQ and H2 extras. Azul Payara Server and Micro 4.1.2.191.61 receives the six security fixes, the OpenMQ Grizzly library port, and updated JDK versions in the Docker images.
What’s New in Payara Community
Payara Community 7.2026.11 (download here) tracks the Payara 7 development line and carries the same five security fixes, plus the managed executor and EclipseLink fixes and a leaner distribution without the OpenMQ and H2 extras.
We recommend upgrading to the latest release for your line, and strongly so given the security fixes. If you upgrade an existing domain in place, remove the vulnerable certificates from its trust store. The full breakdown of the release can be found on Foojay.
FAQ
What security issues are fixed in the November 2026 Azul Payara release?
Five security items are fixed on every supported branch: remote code execution in JMX, a remote admin authentication bypass, CVE-2026-110879 in Jackson, a Hazelcast jackson-core vulnerability, and the vulnerable eMudhra certificates in the Payara trust store. The 6, 5, and 4 lines also carry a Hazelcast backport for CVE-2026-107725 and CVE-2026-107726. The fixes ship in Azul Payara Server and Micro 7.6.0, 6.44.0, 5.93.0, and 4.1.2.191.61.
Does upgrading to the November release remove the vulnerable eMudhra certificates from my existing domains?
No. The fix removes the four vulnerable certificates from Payara’s default trust store, but it only applies to new installations and to domains created with the fixed releases. An in-place upgrade does not normally update the trust store, so on an upgraded domain you must remove the certificates manually and update to a JDK that contains the fix. The Azul Payara Security Advisories page lists the certificate fingerprints.
Which Jakarta EE version does each Payara release line support?
Azul Payara Server & Micro 7 support Jakarta EE 11, with Azul Payara Server 7 certified across the Full Platform, Web Profile, and Core Profile. Azul Payara Server and Micro 6 support Jakarta EE 10, and Azul Payara Server and Micro 5 support Jakarta EE 8 on the javax.* namespace. All of them, along with Payara 4, currently receive monthly security and bug-fix releases.
Can Jakarta EE 10 applications run on a Jakarta EE 11 application server?
Yes. The jakarta.* namespace is stable between Jakarta EE 10 and Jakarta EE 11, so an application built for Jakarta EE 10 deploys on a Jakarta EE 11 runtime without namespace changes. Moving from Azul Payara Server 6 to Azul Payara Server 7 is a runtime upgrade rather than a code rewrite for most applications. Migration assessments are available from Azul for teams planning the move.
How long do application server vendors support older major versions?
Practice varies widely, and many vendors treat upgrading to the current major version as the remedy for a security issue. Azul backports security patches across every supported Azul Payara branch on a published monthly schedule, currently spanning Azul Payara Server and Micro 7, 6, 5, and 4.