CVE-2026-112266

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

GHSA-8v54-r9x8-p94v ↗EUVD-2026-104307 ↗

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.
sgl-project SGLang <= 0.5.22
CWE-187 Partial String Comparison
ETK-2026-2059Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 13h 52msince last run
1h 44mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h58m
0
+4h
+6h
+8h
+10h
+12h

description

SGLang through 0.5.22 can allow one API client to cancel generation work belonging to other clients. Exploitation requires access to the generation API and relies on supplying a short client-selected request identifier before disconnecting.

mitigation

Restrict generation API access to authenticated, trusted clients and isolate tenants where possible. Until an upstream fixed release is available, monitor for abnormal request cancellations and limit exposure of the service to untrusted networks.

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.
0.42%35th percentile
agent run time
1h 44m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 13:55Z
Δ 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-10-19 13:55Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2059",
  "cve_id": "CVE-2026-112266",
  "display_id": "CVE-2026-112266",
  "ghsa_id": "GHSA-8v54-r9x8-p94v",
  "euvd_id": "EUVD-2026-104307",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-request denial of service in SGLang",
  "summary": "SGLang through 0.5.22 can allow one API client to cancel generation work belonging to other clients. Exploitation requires access to the generation API and relies on supplying a short client-selected request identifier before disconnecting.",
  "mitigation": "Restrict generation API access to authenticated, trusted clients and isolate tenants where possible. Until an upstream fixed release is available, monitor for abnormal request cancellations and limit exposure of the service to untrusted networks.",
  "vendor": "sgl-project",
  "product": "SGLang",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.5.22"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "sglang",
      "purl": null
    }
  ],
  "cwes": [
    187
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0042,
  "epss_percentile": 0.3512,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 104.47063595,
  "t0_at": "2026-10-19T13:55:15.822000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T13:55:15.822000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T13:55:15.822000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112266"
    }
  }
}

published 2026-10-19 14:08Z
last change 2026-10-21 05:31Z

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.