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.