Check these three things.
-
System owner: confirm each Payara Server Community 7 server runs 7.2026.11 or later, and check other editions against their own fixed release.
Fixed release by edition
- Include every Payara Server you run, including one a provider runs for you.
- Record for each server:
- Edition.
- Installed version.
- Source of that version.
- Date checked.
- Affected ranges and fixed releases:
- Community 7: affected from 7.2024.1.Alpha1 up to 7.2026.11. Fixed in 7.2026.11.
- Enterprise 7: affected from 7.0.0 up to 7.6.0. Fixed in 7.6.0.
- Enterprise 6: affected from 6.0.0 up to 6.44.0. Fixed in 6.44.0.
- Enterprise 5: affected from 5.20.0 up to 5.93.0. Fixed in 5.93.0.
- Enterprise 4: affected from 4.1.2.191 up to 4.1.2.191.61. Fixed in 4.1.2.191.61.
- Affected ranges with no fixed release established here:
- 6.2022.1 through 6.2025.11.
- 5.2020.2 through 5.2022.5.
- 5.181 through 5.201.2.
- Edition labels:
- The CVE record lists version ranges, not editions.
- Community comes from the release notes titled Azul Payara Community 7.2026.11.
- Enterprise is used here for the release notes titled Azul Payara 7.6.0, 6.44.0, 5.93.0 and 4.1.2.191.61.
- Community 7 version numbers include a year, such as 7.2026.11.
- A fixed release for one edition does not fix another. Do not install an Enterprise version on a Community server.
- The record's default status is unaffected. Versions outside these ranges are not listed as affected.
- An affected release needs its fix even when administration is not reachable today.
-
Network owner: check whether untrusted networks can reach administration on an affected server with an empty administrative password, even if Payara blocks remote administration.
When the risk applies
- The no-sign-in attack in the CVE record needs all of these:
- An affected Payara Server release.
- Network reach to the administration interface.
- A default domain with an empty administrative password.
- A default domain is the administrative setup created with a new installation. The CVE record does not describe the result when a password is set. Treat a reachable affected server with a password as possibly affected.
- Secure admin is Payara's setting for protected administration.
- It is disabled by default when you install the server or create a domain.
- While disabled, Payara normally refuses administrative connections from other hosts.
- The CVE record says this flaw bypasses that restriction. That default does not show a server is safe.
- Which service is affected:
- The flaw is in the administration interface, served by the listener admin-listener on the virtual server __asadmin.
- Hosted applications use separate default listeners: http-listener-1 on port 8080 and http-listener-2 on port 8181.
- Public access to an application does not show whether administration is reachable. It does not rule it out either.
- A reachable sign-in page alone proves neither the flaw nor safety.
- Still unknown: the port and routes your administration listener uses. These sources do not give them. Network owner: confirm them from firewall, proxy and load-balancer records.
- Records to check:
- Network rules for the administration listener.
- Proxy or load-balancer routes to it.
- The period it was reachable, if it was.
- Source and date of each record.
- System owner: record whether each domain's administrative password is empty. Record yes or no, never the password.
- Reach is not evidence of harm.
- The no-sign-in attack in the CVE record needs all of these:
-
Security owner: review administrative changes and deployments on servers that were reachable while affected, including servers already updated.
What the records can show
- Start with servers that ran an affected release while administration was reachable.
- Records to review:
- Administrative configuration changes.
- Application deployments.
- Existing administration access records, if you keep them.
- If a change or deployment nobody approved appears, start response now. Act even if this CVE is not shown as the cause.
- Limits:
- An update does not rule out earlier harm.
- A clean record does not prove nothing changed.
- A missing record leaves the question open.
- No entry in the checked KEV catalog does not mean no exploitation.
A server on a line with a fixed release needs that release. If administration was reachable, review change and deployment records now.
Do Now
- System owner: update Payara Server Community 7 to 7.2026.11, and other editions to their own fixed release.
Fixed release for each line
- Use the fixed release for the server's own edition and line:
- Community 7: 7.2026.11.
- Enterprise 7: 7.6.0.
- Enterprise 6: 6.44.0.
- Enterprise 5: 5.93.0.
- Enterprise 4: 4.1.2.191.61.
- Azul's release notes for each of these list issue FISH-14855. The CVE record lists no solution.
- GitHub published Community 7.2026.11 on November 11, 2026. These sources do not date the other release-note pages.
- Record after the work:
- Server.
- Edition.
- Installed version.
- Source of that version.
- Date checked.
- An update does not rule out earlier harm.
- Use the fixed release for the server's own edition and line:
- System owner: ask the provider for a supported migration path for older Community 5 and 6 servers, which have no fixed release here.
What to ask the provider
- Affected ranges without a fixed release in these sources:
- 6.2022.1 through 6.2025.11.
- 5.2020.2 through 5.2022.5.
- 5.181 through 5.201.2.
- Ask:
- Which supported release fixes issue FISH-14855 for that server.
- How to move to it.
- Do not install an Enterprise version on a Community server.
- Until the move:
- Network owner: limit administration reach to trusted networks.
- Security owner: review administrative changes for that period.
- Record:
- Provider answer.
- Planned release.
- Date of the answer.
- Affected ranges without a fixed release in these sources:
- Network owner: limit administration reach to trusted networks; this does not replace the fixed release.
What this does and does not do
- It reduces who can reach the administration listener, admin-listener.
- These sources do not name a network limit as the fix.
- Application access on ports 8080 or 8181 does not answer this.
- If reach is already limited, record that evidence.
- Record:
- Server.
- Who can reach administration.
- Source of the record.
- Date checked.
- System owner: set an administrative password where none is set; the CVE record does not confirm this blocks the flaw.
What this does not prove
- The no-sign-in attack needs an empty administrative password on a default domain.
- The CVE record does not describe the result when a password is set.
- The fixed release is required even so.
- Record:
- Domain.
- Whether a password is set.
- Date checked.
- Never record the password.
- Security owner: preserve existing administrative and deployment records from servers that were reachable while affected.
What to keep and when to escalate
- Copy them before updates or restarts can replace them.
- Keep:
- Configuration change records.
- Deployment records.
- Administration access records, if you keep them.
- If a change or deployment nobody approved appears, start response now.
- Record:
- Records kept.
- Source of the records.
- Period covered.
- Date preserved.
- Operations owner: review logs and uptime alerts for unexpected restarts or outages on servers that were reachable while affected.
When to escalate
- If customer or staff service was interrupted, handle it as a service incident now.
- Send signs of unapproved administrative changes to the Security owner.
- An outage does not prove this CVE.
- An outage does not prove a break-in.
- Record:
- Records reviewed.
- Source of the records.
- Date reviewed.
Do Next
- Security owner: recheck the KEV catalog and the CVE record for a CISA assessment, because the checked catalog predates this CVE.
What the checked records show
- KEV catalog:
- Version 2026.11.10, released November 10, 2026.
- Retrieved November 12, 2026.
- No matching entry.
- This CVE was published November 12, 2026, after that catalog release.
- The CVE record retrieved November 12, 2026 had no CISA ADP assessment.
- A later KEV listing would show known exploitation somewhere. It would not show your servers were attacked.
- Neither current result shows that no exploitation happened.
- KEV catalog:
Check your own records.
- Use your approved AI tool.
- Require evidence. Flag unknowns.
Read the prompt
The reported finding
Administration REST interface authentication bypass
Original advisory →- Required conditions
- An affected Payara Server release listed in the CVE record.
- Network reach to the administration REST interface. A REST interface lets programs send administration requests over the web.
- For the no-credential path, a default domain with an empty administrative password.
- Reported outcome
- Payara, as the CNA, says the flaw lets a “remote, unauthenticated attacker to bypass secure-admin remote-access restrictions”.
- It says success “grants execution of arbitrary administrative commands, equivalent to complete compromise of the server.”
- Payara's CVSS 4.0 base score is 9.3, Critical. This is technical severity, not evidence of exploitation.
- Limits:
- The record does not describe the result when an administrative password is set.
- The record's solutions field is empty.
- The record has no CISA ADP assessment.
Fix guidance
- Fixed releases, each listing issue FISH-14855:
- Boundaries:
- The CVE record names no editions. Edition labels follow the release-note titles.
- No fixed release is established here for 6.2022.1 through 6.2025.11.
- No fixed release is established here for 5.2020.2 through 5.2022.5.
- No fixed release is established here for 5.181 through 5.201.2.
- A fixed release for one edition does not fix another.
- Dates:
- GitHub published Community release payara-server-7.2026.11 on November 11, 2026.
- The CVE record was published November 12, 2026.
- These sources do not date the other release-note pages.
- A server updated after a period of reachable administration still needs its change and deployment records reviewed.
What IntegrityLab.ai can check
- The authorized unauthenticated web discovery records:
- Status.
- Page title.
- Content length.
- Server identification.
- Limits:
- It has no check for CVE-2026-110003.
- It does not check Payara administrative security.
- It does not establish:
- Installed version.
- Fix status.
- Configuration.
- Compromise.
- A front server can hide the backend. Missing identification does not rule Payara out.
- A relevant observation is a lead for the owner, not detection of this CVE.
- System owner: establish the software and configuration conditions for exposure from authorized internal records.
- Network owner: establish administration reach from authorized internal records.
Sources and vendor guidance
- Original advisory: CVE-2026-110003 record
- Vendor guidance: Azul Payara Community 7.2026.11 release notes
- Azul Payara 7.6.0 release notes
- Azul Payara 6.44.0 release notes
- Azul Payara 5.93.0 release notes
- Azul Payara 4.1.2.191.61 release notes
- Payara documentation: managing administrative security
- Payara documentation: HTTP connectivity and listeners
- GitHub release record: payara-server-7.2026.11
- CISA KEV catalog data