← back to feed
CVE-2026-110003

CVE-2026-110003

validatedZero produced an exploit or a check.

GHSA-gv3m-v36g-qfr6 ↗EUVD-2026-124331 ↗

check availableZero validated a working check for it.proven exploitableZero has validated a full working exploit.
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
fixed in 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61
CWE-288 Authentication Bypass Using an Alternate Path or Channel
ETK-2026-4255Zero'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
+51mTTV
32mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck + exploit+51m
0
+10min
+20min
+30min
+40min

description

Payara Server administration REST interfaces are affected by an authentication bypass that can let an unauthenticated remote attacker run administrative commands. Exposure requires the administration interface to be reachable and is described as exploitable on default domains using an empty administrative password.

mitigation

Upgrade Payara Server to 7.6.0, 7.2026.11, 6.44.0, 5.93.0, or 4.1.2.191.61, as appropriate for your release line. Set a non-empty administrative password and restrict remote access to the administration interface.

fixed in 7.6.0, 7.2026.11, 6.44.0, 5.93.0, 4.1.2.191.61

check
available
exploit
yes
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.
deterministic
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
32m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 08:43Z
Δ 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

Differential: the exploit fired on the vulnerable build and stayed silent on the patched one.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-4255",
  "cve_id": "CVE-2026-110003",
  "display_id": "CVE-2026-110003",
  "ghsa_id": "GHSA-gv3m-v36g-qfr6",
  "euvd_id": "EUVD-2026-124331",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Payara Server administration REST interface",
  "summary": "Payara Server administration REST interfaces are affected by an authentication bypass that can let an unauthenticated remote attacker run administrative commands. Exposure requires the administration interface to be reachable and is described as exploitable on default domains using an empty administrative password.",
  "mitigation": "Upgrade Payara Server to 7.6.0, 7.2026.11, 6.44.0, 5.93.0, or 4.1.2.191.61, as appropriate for your release line. Set a non-empty administrative password and restrict remote access to the administration interface.",
  "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
    }
  ],
  "cwes": [
    288
  ],
  "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": true,
  "check_confidence_basis": "differential",
  "exploit": true,
  "pipeline_minutes": 31.798647,
  "t0_at": "2026-11-12T08:43:19.548000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-12T09:34:07.882588+00:00",
      "days": 0.03528165032407407,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T08:43:19.548000+00:00",
      "url": null
    },
    "exploit": {
      "at": "2026-11-12T09:34:07.882588+00:00",
      "days": 0.03528165032407407,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T08:43:19.548000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-12T08:43:19.548000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T08:43:19.548000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110003"
    }
  }
}

published 2026-11-12 09:02Z
last change 2026-11-12 10:03Z

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.