Azul says the weakness can let a remote attacker bypass admin listener access restrictions when secure admin is disabled.The NVD record describes an additional condition: a domain with an empty administrative password. Under that condition, unauthenticated access can lead to administrative commands and full server compromise. NVD lists a CVSS 4.0 score of 9.3 Critical.
What it allows
How Does CVE-2026-110003 Bypass Payara Administration Controls?
According to NVD, the REST authentication path checks for a token field before it validates the token. The field can bypass the check that would reject remote administration when secure admin is disabled.
An invalid token can then fall through to password authentication. On a default domain with an empty administrative password, that fallback can succeed without credentials. NVD says the resulting administrative access permits arbitrary administrative commands and can compromise the server.
This REST path is separate from CVE-2026-90908. Azul describes that sibling flaw as a JMX/RMI authentication error involving how a remote connection is classified. Both appear in the same security list and have a 7.6.0 fix, but they require different checks.
How Should Teams Prioritize This Payara Flaw?
The NVD record assigns CVSS 4.0 9.3 Critical as a secondary assessment. The potential impact warrants prompt review of exposed administration listeners and domains with empty admin passwords. Our vulnerability prioritization explainer distinguishes severity from evidence of exploitation.
Brandefense Blackhole counted two dark-chat posts mentioning CVE-2026-110003 from August 14 through November 12, 2026. These are two posts, not verified incidents or proof of successful exploitation. The CVE was absent from CISA KEV catalog version 2026.11.10.
Who is affected
Which Azul Payara Release Fixes CVE-2026-110003?
Azul marks this administration interface issue fixed in Payara 7.6.0 through additional validation. The opened security list does not specify a complete affected-version range. NVD had not analyzed affected configurations in its November 12 record.
Inventory Payara servers and identify the installed release, secure admin setting, and administrative password state. Prioritize reachable administration listeners with secure admin disabled or an empty password. Upgrade to the applicable vendor-fixed release and verify the installed version after maintenance.
Azul Payara Community 7.2026.11 release notes also list a remote admin authentication bypass fix. That release note names the unvalidated auth-token problem, while the Azul Payara security list identifies 7.6.0 for CVE-2026-110003. Confirm the product edition before selecting an update.
Timeline
- 2026-11-12
NVD published CVE-2026-110003. Azul lists the administration interface weakness as fixed in Payara 7.6.0.
What to do
-
Identify exposed administration listeners
Inventory Azul Payara instances and determine whether their administration listeners are reachable from untrusted networks. Prioritize systems with secure admin disabled.
-
Check administrator password configuration
Verify that every domain has a nonempty administrative password. NVD describes successful unauthenticated access on default domains configured with an empty password.
-
Apply the edition-appropriate fix
Azul lists 7.6.0 as the fixed Azul Payara release. Its Community 7.2026.11 release notes list the same remote admin authentication bypass fix. Confirm edition and version after upgrading.
-
Review administrative activity
Brandefense recommends reviewing administration access logs and changes for unexpected commands or configuration changes while an exposed instance awaited remediation.
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-110003 in Brandefense Atlas
The Atlas record of CVE-2026-110003: 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 is CVE-2026-110003?
It is an Azul Payara administration REST authentication bypass. NVD says an empty administrative password on a default domain can let an unauthenticated remote attacker execute administrative commands.
Which release fixes CVE-2026-110003?
Azul lists Payara 7.6.0 as fixed through additional validation. The Community 7.2026.11 notes also list the remote admin authentication bypass fix.
Is CVE-2026-110003 the same as CVE-2026-90908?
No. CVE-2026-110003 concerns the REST administration path. Azul describes CVE-2026-90908 as a separate JMX/RMI connection classification flaw.
Has exploitation of CVE-2026-110003 been confirmed?
The cited records do not establish a confirmed incident. Two Brandefense Blackhole dark-chat mentions from August 14 to November 12, 2026, indicate discussion, not successful exploitation.
Sources
- Azul Payara Security AdvisoriesAzul
- CVE-2026-110003 DetailNational Vulnerability Database
- Azul Payara Community 7.2026.11 Release NotesAzul
- Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency