Azul says GenericAdminAuthenticator may classify a remote connection as local, permitting an unauthenticated attacker to obtain administrative JMX access.Administrative access to the MBean server may lead to code execution as the Payara service account. Payara Micro is affected only when its JMX connector is enabled, according to the NVD record.
What it allows
How Does CVE-2026-90908 Cross the JMX/RMI Trust Boundary?
Azul says GenericAdminAuthenticator can mistake a remote JMX/RMI connection for a local one. The flawed host check then permits administrative JMX access when secure admin is disabled.
An unauthenticated remote attacker may reach the MBean server and execute code with the Payara service account's privileges. This is an authentication boundary failure, not a flaw in an application's REST endpoint.
Azul lists CVE-2026-110003 separately for an administration interface weakness. Its advisory gives that issue a different description and fix, so the two CVEs should be tracked separately.
What Is Known About CVE-2026-90908 Exploitation?
NVD records a CVSS 4.0 score of 9.3 Critical from a secondary source. Its record provides no CVSS 3.1 score, and the Azul advisory lists its own score as TBD.
The CISA KEV snapshot released November 10, 2026, does not list this CVE. That snapshot predates NVD publication on November 12, so it cannot settle whether exploitation later occurred.
Brandefense Blackhole counted two dark-chat posts mentioning CVE-2026-90908 between August 14 and November 12, 2026. The unit is posts, and the count is a discussion signal, not evidence of intrusion or successful exploitation.
Who is affected
Which Payara Deployments Need Review?
NVD names Azul Payara Server and Azul Payara Micro. Micro is affected only when its JMX connector is enabled, so operators should check that setting before treating every Micro instance alike.
Azul's advisory names 7.6.0 as the release containing the JMX authentication fix. Azul's release notes also list the JMX remote code execution fix under FISH-14190 for Azul Payara 4.1.2.191.61, 5.93.0, 6.44.0, and 7.6.0, plus Community 7.2026.11.
Our reading links those branch notes to this flaw because they share the JMX fix identifier and NVD cites the notes. The advisory does not give a complete affected-version range for each branch.
How Should Defenders Prioritize the Fix?
Inventory Server and Micro installations, recording the branch, build, secure-admin setting, JMX connector state, and network reachability. Prioritize reachable JMX management surfaces because the described attack requires no authentication.
Move each deployment to its applicable fixed branch release after confirming support and compatibility with Azul. For Micro, verify the JMX connector setting; restrict management network access while the release update is scheduled.
After updating, verify the installed build and review administrative JMX access for unexpected changes. These inventory, exposure-reduction, and review steps are Brandefense recommendations based on the vendor's attack path.
The vulnerability management guide helps structure the rollout. See patch management for release verification and external attack surface management for exposed management services.
Timeline
- 2026-11-10
CISA KEV catalog version 2026.11.10 was released without this CVE; this was before the NVD publication date.
- 2026-11-12
NVD published CVE-2026-90908 and recorded a secondary-source CVSS 4.0 score of 9.3 Critical.
What to do
-
Identify exposed JMX management
Inventory Payara Server and Micro installations. Check JMX reachability, secure-admin configuration, and whether the Micro JMX connector is enabled.
-
Apply the appropriate Azul release
Use the branch release notes to plan the update: Azul Payara 4.1.2.191.61, 5.93.0, 6.44.0, or 7.6.0; Community 7.2026.11.
-
Verify and review
Confirm the installed build after deployment. Review administrative JMX access and restrict management network exposure during the update window.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-90908 in Brandefense Atlas
The Atlas record of CVE-2026-90908: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What does CVE-2026-90908 allow?
Azul says a remote unauthenticated attacker may bypass the JMX/RMI administrative host check. Administrative MBean access can lead to code execution as the Payara service account.
Is Azul Payara Micro always affected?
No. The NVD record says Micro is affected only when its JMX connector is enabled.
Is this the Payara REST administration flaw?
No. Azul lists CVE-2026-110003 separately for a different administration interface weakness. CVE-2026-90908 concerns JMX/RMI authentication.
Which Azul releases include the JMX fix?
The advisory names 7.6.0. Azul release notes list the JMX fix in Azul Payara 4.1.2.191.61, 5.93.0, 6.44.0, and 7.6.0, and Community 7.2026.11.
Is CVE-2026-90908 in CISA KEV?
It was absent from catalog version 2026.11.10. That catalog snapshot predates the November 12 NVD publication and does not establish exploitation status.
Sources
- Security AdvisoriesAzul
- Azul Payara 7.6.0 Release NotesAzul
- Azul Payara 6.44.0 Release NotesAzul
- Azul Payara 5.93.0 Release NotesAzul
- Azul Payara 4.1.2.191.61 Release NotesAzul
- Azul Payara Community 7.2026.11 Release NotesAzul
- CVE-2026-90908 DetailNational Vulnerability Database
- Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency