Azul Payara Server up to 7.2026.10 Administration REST Interface X-GlassFish-authToken access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in Azul Payara Server up to 7.2026.10 and classified as critical. The impacted element is an unknown function of the component Administration REST Interface. Executing a manipulation of the argument X-GlassFish-authToken can lead to access control. This vulnerability is registered as CVE-2026-110003. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Azul Payara Server up to 7.2026.10. It has been declared as critical. This vulnerability affects an unknown code of the component Administration REST Interface. The manipulation of the argument X-GlassFish-authToken with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at docs.azul.com. This vulnerability was named CVE-2026-110003 since 10/13/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading to version 4.1.2.191.61, 5.93.0, 6.44.0, 7.6.0 or 7.2026.11 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 5.0
- 5.1
- 5.2
- 5.3
- 5.4
- 5.5
- 5.6
- 5.7
- 5.8
- 5.9
- 5.10
- 5.11
- 5.12
- 5.13
- 5.14
- 5.15
- 5.16
- 5.17
- 5.18
- 5.19
- 5.20
- 5.21
- 5.22
- 5.23
- 5.24
- 5.25
- 5.26
- 5.27
- 5.28
- 5.29
- 5.30
- 5.31
- 5.32
- 5.33
- 5.34
- 5.35
- 5.36
- 5.37
- 5.38
- 5.39
- 5.40
- 5.41
- 5.42
- 5.43
- 5.44
- 5.45
- 5.46
- 5.47
- 5.48
- 5.49
- 5.50
- 5.51
- 5.52
- 5.53
- 5.54
- 5.55
- 5.56
- 5.57
- 5.58
- 5.59
- 5.60
- 5.61
- 5.62
- 5.63
- 5.64
- 5.65
- 5.66
- 5.67
- 5.68
- 5.69
- 5.70
- 5.71
- 5.72
- 5.73
- 5.74
- 5.75
- 5.76
- 5.77
- 5.78
- 5.79
- 5.80
- 5.81
- 5.82
- 5.83
- 5.84
- 5.85
- 5.86
- 5.87
- 5.88
- 5.89
- 5.90
- 5.91
- 5.92
- 5.201.0
- 5.201.1
- 5.201.2
- 5.2022.0
- 5.2022.1
- 5.2022.2
- 5.2022.3
- 5.2022.4
- 5.2022.5
- 6.0
- 6.1
- 6.2
- 6.3
- 6.4
- 6.5
- 6.6
- 6.7
- 6.8
- 6.9
- 6.10
- 6.11
- 6.12
- 6.13
- 6.14
- 6.15
- 6.16
- 6.17
- 6.18
- 6.19
- 6.20
- 6.21
- 6.22
- 6.23
- 6.24
- 6.25
- 6.26
- 6.27
- 6.28
- 6.29
- 6.30
- 6.31
- 6.32
- 6.33
- 6.34
- 6.35
- 6.36
- 6.37
- 6.38
- 6.39
- 6.40
- 6.41
- 6.42
- 6.43
- 6.2025.0
- 6.2025.1
- 6.2025.2
- 6.2025.3
- 6.2025.4
- 6.2025.5
- 6.2025.6
- 6.2025.7
- 6.2025.8
- 6.2025.9
- 6.2025.10
- 6.2025.11
- 7.0
- 7.1
- 7.2
- 7.3
- 7.4
- 7.5
- 7.2026.0
- 7.2026.1
- 7.2026.2
- 7.2026.3
- 7.2026.4
- 7.2026.5
- 7.2026.6
- 7.2026.7
- 7.2026.8
- 7.2026.9
- 7.2026.10
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Payara Server 4.1.2.191.61/5.93.0/6.44.0/7.6.0/7.2026.11
Timeline
10/13/2026 CVE reserved11/12/2026 Advisory disclosed
11/12/2026 VulDB entry created
11/12/2026 VulDB entry last update
Sources
Advisory: docs.azul.comStatus: Confirmed
CNA: Payara
CVE: CVE-2026-110003 (🔒)
GCVE (CVE): GCVE-0-2026-110003
GCVE (VulDB): GCVE-100-436300
Entry
Created: 11/12/2026 10:00Changes: 11/12/2026 10:00 (67)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.