CVE
Azul Payara Server auth bypass in administration REST interface
- Exploited
- No known exploitation
- Fix
- Fixed in 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.65% · 51st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
A remote attacker can reach the administration REST interface of Azul Payara Server without logging in, by sending a crafted X-GlassFish-authToken header that skips the remote-access restriction and falls through to password-based login. On default domains with an empty administrative password, this lets the attacker run arbitrary administrative commands, which amounts to full control of the server.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A vulnerability in the administration REST interface of Azul Payara allows a remote, unauthenticated attacker to bypass secure-admin remote-access restrictions by supplying an arbitrary value in the X-GlassFish-authToken HTTP header. The header's presence waives the remote-rejection check before the token is validated, and an invalid token falls through to password-based authentication, which succeeds without credentials on default domains configured with an empty administrative password. Successful exploitation grants execution of arbitrary administrative commands, equivalent to complete compromise of the server.
Who should check
Teams running Azul Payara Server 4.x builds before 4.1.2.191.61 with the admin REST interface exposed
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-110003 (Azul Payara Administration REST Interface Authentication Bypass via X-GlassFish-authToken Header Leading to Remote Code Execution), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-110003 (entry last updated 2026-11-12):
Affected:
- Azul Payara Payara Server: from 7.0.0, fixed in 7.6.0; from 7.2024.1.Alpha1, fixed in 7.2026.11; from 6.0.0, fixed in 6.44.0; from 6.2022.1, through 6.2025.11; from 5.20.0, fixed in 5.93.0; from 5.181, through 5.201.2; from 5.2020.2, through 5.2022.5; from 4.1.2.191, fixed in 4.1.2.191.61
Fixed versions: 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-110003 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110003 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://docs.azul.com/payara/version/4/release-notes/release-notes-4.1.2.191.61.html
- https://docs.azul.com/payara/version/5/release-notes/release-notes-5.93.0.html
- https://docs.azul.com/payara/version/6/release-notes/release-notes-6.44.0.html
- https://docs.azul.com/payara/release-notes/release-notes-7.6.0.html
- https://docs.azul.com/payara-community/release-notes/release-notes-7.2026.11.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-110003
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110003"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Azul Payara Payara Server
From 7.0.0 · fixed in 7.6.0; From 7.2024.1.Alpha1 · fixed in 7.2026.11; From 6.0.0 · fixed in 6.44.0; From 6.2022.1 · through 6.2025.11; From 5.20.0 · fixed in 5.93.0; From 5.181 · through 5.201.2; From 5.2020.2 · through 5.2022.5; From 4.1.2.191 · fixed in 4.1.2.191.61
Evidence 7
Vendor advisory · 5
Establishes: Affected and fixed versions.
- Link
- Link
- Link
- Link
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-110003
Is CVE-2026-110003 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-110003?
Payara Server: from 7.0.0 before 7.6.0; from 7.2024.1.Alpha1 before 7.2026.11; from 6.0.0 before 6.44.0; from 6.2022.1 through 6.2025.11; from 5.20.0 before 5.93.0; from 5.181 through 5.201.2; from 5.2020.2 through 5.2022.5; from 4.1.2.191 before 4.1.2.191.61.Source: cve.now feed data
How do I fix CVE-2026-110003?
Upgrade to a fixed version: 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61.Source: cve.now feed data