SGLang up to 0.5.20 ZMQ Message Decoder pickle.loads deserialization

Summaryinfo

A vulnerability has been found in SGLang up to 0.5.20 and classified as critical. Impacted is the function pickle.loads of the component ZMQ Message Decoder. This manipulation causes deserialization. This vulnerability appears as CVE-2026-93034. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in SGLang up to 0.5.20 and classified as critical. Affected by this vulnerability is the function pickle.loads of the component ZMQ Message Decoder. The manipulation with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

SGLang contains an arbitrary code execution vulnerability caused by the ZMQ message decoder unconditionally deserializing PickleWrapper payloads via pickle.loads() in _maybe_unwrap_pickle without type allowlisting or authentication; this vulnerability persists via the msgpack path even when SGLANG_USE_PICKLE_IPC is disabled, and becomes remotely exploitable if data-parallel attention is enabled with a non-loopback --dist-init-addr setting.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-93034 since 09/17/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/08/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• SGLang

Version

• 0.5.0
• 0.5.1
• 0.5.2
• 0.5.3
• 0.5.4
• 0.5.5
• 0.5.6
• 0.5.7
• 0.5.8
• 0.5.9
• 0.5.10
• 0.5.11
• 0.5.12
• 0.5.13
• 0.5.14
• 0.5.15
• 0.5.16
• 0.5.17
• 0.5.18
• 0.5.19
• 0.5.20

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion