Cyber Resilience

CVE-2026-3060

RCE in Lmsys Sglang 0.5.5 – 0.5.9

Published
12 March 2026
Modified
07 April 2026
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.012 64th percentile
Risk Priority 75 floored blend · peak EPSS

Summary

CVE-2026-3060 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Lmsys Sglang. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 36% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

SGLang's encoder parallel disaggregation system contains a deserialization flaw in its disaggregation module that invokes pickle.loads() on untrusted data without any authentication checks. The affected component is exposed in the encode_receiver.py path of the SGLang project and is tracked as CVE-2026-3060 with a CVSS 3.1 score of 9.8 and CWE-502.

An unauthenticated network attacker can supply a malicious serialized payload to the disaggregation endpoint and obtain arbitrary remote code execution, resulting in full confidentiality, integrity, and availability impact on the host. The vulnerability requires no user interaction or credentials and can be reached directly over the network.

The project addressed the issue in release v0.5.10 via pull request 20904, which updates the disaggregation handling to avoid unsafe pickle usage. The referenced Orca Security advisory and GitHub commit history document the change and recommend upgrading to the patched version.

EPSS remains low and unchanged at 0.0194 with no observed rise after disclosure. The finding is specific to an LLM inference framework and underscores risks in distributed serving components that accept serialized inputs.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

SGLang' encoder parallel disaggregation system is vulnerable to unauthenticated remote code execution through the disaggregation module, which deserializes untrusted data using pickle.loads() without authentication.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-3989Same product: Lmsys Sglang
CVE-2026-3059Same product: Lmsys Sglang
CVE-2026-7301Same product: Lmsys Sglang
CVE-2026-14890Same product: Lmsys Sglang
CVE-2026-15969Same product: Lmsys Sglang
CVE-2026-7304Same product: Lmsys Sglang
CVE-2026-15976Same product: Lmsys Sglang
CVE-2026-15978Same product: Lmsys Sglang
CVE-2026-7302Same product: Lmsys Sglang
CVE-2026-10775Same product: Lmsys Sglang

Affected Assets

lmsys
sglang
0.5.5 — 0.5.9

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can uncover deserialization flaws before deployment.

Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

Integrity verification tools can detect malformed or tampered serialized data after the fact.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 none match
prevents

PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.

prevents

Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.

finds

Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.

none

Mandatory malware scanning of data received over networks or storage media intercepts malicious serialized payloads before they are deserialized by the target application.

References