CVE-2026-14890

Answer in brief

CVE-2026-14890 records a Critical severity (CVSS 9.1) vulnerability in CVE-2026-14890. The current sources do not mark it as known exploited. The current feed maps 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 Jul 16, 2026Updated Aug 10, 2026Source checked Sep 17, 2026First seen by HOL Jul 16, 2026Material review Aug 10, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.1
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Not reported

Why this deserves its current priority

CVSS is 9.1. 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). Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:a:lmsys:sglang::::::::	Not reported	Not reported

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
SGLang/SGLanggeneric	0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for 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
Jul 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 16, 2026

Sources and claim methodology

Upstream source description

SGLang uses an expert-parallel backup subsystem that exposes a ZeroMQ PULL socket on a routable network interface that does not contain authentication or deserialization safeguards, allowing an attacker to provide a malicious pickle file that results in unauthenticated remote code execution when the feature is enabled and the service is reachable over the network.

Quoted source text, attributed separately from HOL analysis.