Contact us
← Article questionsWhat should we do?

CVEHit Business Advisory by IntegrityLab.ai

What should we do?

Payara Server administration takeover — CVE-2026-110003: Business Triage

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.
  • 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.
  • 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.

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…