← back to feed
CVE-2026-90908

CVE-2026-90908

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qcx2-v78c-8gq4 ↗EUVD-2026-124332 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Azul Payara Payara Server >= 7.0.0, < 7.6.0; >= 7.2024.1.Alpha1, < 7.2026.11; >= 6.0.0, < 6.44.0; >= 6.2022.1, <= 6.2025.11; >= 5.20.0, < 5.93.0; >= 5.181, <= 5.201.2; >= 5.2020.2, <= 5.2022.5; >= 4.1.2.191, < 4.1.2.191.61; >= 4.1.1.154.1, < 4.1.2.191.61
fixed in 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61
CWE-807 Reliance on Untrusted Inputs in a Security Decision
ETK-2026-4256Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.3cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
3h 27msince last run
37mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h46m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Payara Server is affected by an authentication-control bypass in its JMX/RMI administrative component; Payara Micro is affected when its JMX connector is enabled. A remote attacker without credentials may obtain MBean server administrative access and potentially execute code by evading client-address-based access restrictions.

mitigation

Upgrade Payara Server and Payara Micro to the applicable fixed release: 7.6.0, 7.2026.11, 6.44.0, 5.93.0, or 4.1.2.191.61. Until upgraded, disable the Payara Micro JMX connector where it is not required and restrict JMX/RMI administrative access to trusted networks.

fixed in 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 08:53Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-12 08:53Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-90908

this entry in the feed

GET /api/v1/feed/CVE-2026-90908

{
  "etk_id": "ETK-2026-4256",
  "cve_id": "CVE-2026-90908",
  "display_id": "CVE-2026-90908",
  "ghsa_id": "GHSA-qcx2-v78c-8gq4",
  "euvd_id": "EUVD-2026-124332",
  "status": "published",
  "anchor_state": "anchored",
  "title": "JMX/RMI authentication bypass in Payara Server and Payara Micro",
  "summary": "Payara Server is affected by an authentication-control bypass in its JMX/RMI administrative component; Payara Micro is affected when its JMX connector is enabled. A remote attacker without credentials may obtain MBean server administrative access and potentially execute code by evading client-address-based access restrictions.",
  "mitigation": "Upgrade Payara Server and Payara Micro to the applicable fixed release: 7.6.0, 7.2026.11, 6.44.0, 5.93.0, or 4.1.2.191.61. Until upgraded, disable the Payara Micro JMX connector where it is not required and restrict JMX/RMI administrative access to trusted networks.",
  "vendor": "Azul Payara",
  "product": "Payara Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.0.0, < 7.6.0",
        ">= 7.2024.1.Alpha1, < 7.2026.11",
        ">= 6.0.0, < 6.44.0",
        ">= 6.2022.1, <= 6.2025.11",
        ">= 5.20.0, < 5.93.0",
        ">= 5.181, <= 5.201.2",
        ">= 5.2020.2, <= 5.2022.5",
        ">= 4.1.2.191, < 4.1.2.191.61"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.6.0",
        "7.2026.11",
        "6.44.0",
        "5.93.0",
        "4.1.2.191.61"
      ],
      "package_name": "Payara Server",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.0.0, < 7.6.0",
        ">= 7.2024.1.Alpha1, < 7.2026.11",
        ">= 6.0.0, < 6.44.0",
        ">= 6.2022.1, <= 6.2025.11",
        ">= 5.20.0, < 5.93.0",
        ">= 5.181, <= 5.201.2",
        ">= 5.2020.2, <= 5.2022.5",
        ">= 4.1.1.154.1, < 4.1.2.191.61"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.6.0",
        "7.2026.11",
        "6.44.0",
        "5.93.0",
        "4.1.2.191.61"
      ],
      "package_name": "Payara Micro",
      "purl": null
    }
  ],
  "cwes": [
    807
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 36.7653667,
  "t0_at": "2026-11-12T08:53:29.043000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T08:53:29.043000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T08:53:29.043000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-90908"
    }
  }
}

published 2026-11-12 09:02Z
last change 2026-11-12 12:51Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.