Contact us
← Article questionsWhat’s the evidence?

CVEHit Business Advisory by IntegrityLab.ai

What’s the evidence?

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

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.
    This can help an owner find a service to investigate.
  • 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.

How to read the score

Payara (CNA) CVSS 4.0: 9.3 (Critical). Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

← 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…