Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Payara

CVE-2026-90908: Azul Payara JMX/RMI Remote Authentication Bypass Leading to Remote Code Execution via GenericAdminAuthenticator

CriticalCVSS 9.3 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 37/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.53% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Azul Payara Payara Micro 5.93.0, 6.44.0, 7.6.0; Azul Payara Payara Server 5.93.0, 6.44.0, 7.6.0.

Low priority for now. Upgrade to Azul Payara Payara Micro 5.93.0, 6.44.0, 7.6.0; Azul Payara Payara Server 5.93.0, 6.44.0, 7.6.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Nov 12, 2026
Updated
Nov 12, 2026
EPSS
0.5% · 45th percentile

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CNA vs NVD score

NVD
—
CNA · Payara
9.3
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-90908

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for azul payara records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Payara). Independent of NVD's CPE analysis and usually ahead of it.

  • Azul Payara Payara Micro

    • 7.0.0 and later · before 7.6.0affected · semver
    • 7.2024.1.Alpha1 and later · before 7.2026.11affected
    • 6.0.0 and later · before 6.44.0affected · semver
    • 6.2022.1 and later · up to and including 6.2025.11affected
    • 5.20.0 and later · before 5.93.0affected · semver
    • 5.181 and later · up to and including 5.201.2affected
    • 5.2020.2 and later · up to and including 5.2022.5affected
    • 4.1.1.154.1 and later · before 4.1.2.191.61affected

  • Azul Payara Payara Server

    • 7.0.0 and later · before 7.6.0affected · semver
    • 7.2024.1.Alpha1 and later · before 7.2026.11affected
    • 6.0.0 and later · before 6.44.0affected · semver
    • 6.2022.1 and later · up to and including 6.2025.11affected
    • 5.20.0 and later · before 5.93.0affected · semver
    • 5.181 and later · up to and including 5.201.2affected
    • 5.2020.2 and later · up to and including 5.2022.5affected
    • 4.1.2.191 and later · before 4.1.2.191.61affected

Same product

azul payara: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-110003Azul Payara Administration REST Interface Authentication Bypass via X-GlassFish-authToken Header Leading to Remote Code Execution
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Azul Payara Payara Micro5.93.0Vendor (CNA)
Azul Payara Payara Micro6.44.0Vendor (CNA)
Azul Payara Payara Micro7.6.0Vendor (CNA)
Azul Payara Payara Server5.93.0Vendor (CNA)
Azul Payara Payara Server6.44.0Vendor (CNA)
Azul Payara Payara Server7.6.0Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 13, 2026+1 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

CWE-807 · Reliance on Untrusted Inputs in a Security Decision

CVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records