CVE-2026-93088

Answer in brief

CVE-2026-93088 records a Unknown severity vulnerability in CVE-2026-93088. The current sources do not mark it as known exploited. The current feed maps SGLang/SGLang (generic), SGLang/SGLang (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 22, 2026Updated Sep 22, 2026Source checked Sep 22, 2026First seen by HOL Sep 22, 2026Material review Sep 22, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps SGLang/SGLang (generic), SGLang/SGLang (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
SGLang/SGLanggeneric	0.5.11	Not reported
SGLang/SGLanggeneric	>=0.5.11 <=0.5.14	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for SGLang/SGLang, SGLang/SGLang.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 22, 2026

Sources and claim methodology

Upstream source description

SGLang's multimodal generation runtime is vulnerable to unauthenticated arbitrary code execution because the disaggregated-diffusion orchestrator's DiffusionServer binds an unauthenticated ZeroMQ ROUTER socket to a network interface and passes the final frame of received multipart messages directly to pickle.loads() before any validation occurs.

Quoted source text, attributed separately from HOL analysis.