CVE-2026-93034 SGLang CVE debrief

Who should care

Defenders responsible for SGLang deployments, especially those with data-parallel attention enabled and non-loopback --dist-init-addr settings, should assess exposure and prioritize verification and potential mitigations.

Why it matters

CVE-2026-93034 is an arbitrary code execution vulnerability in SGLang that can be exploited remotely under certain configurations. Defenders should prioritize verifying exposure and potential mitigations.

• Verify exposure in SGLang deployments with data-parallel attention enabled
• Assess the impact of disabling SGLANG_USE_PICKLE_IPC
• Monitor for potential exploitation attempts

Technical summary

The SGLang library contains an arbitrary code execution vulnerability due to 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 vulnerability can be addressed by verifying exposure in SGLang deployments, especially those with data-parallel attention enabled and non-loopback --dist-init-addr settings, and prioritizing mitigations such as disabling SGLANG_USE_PICKLE_IPC or updating SGLang.

Defensive priority

Defenders should prioritize verifying exposure in SGLang deployments, especially those with data-parallel attention enabled and non-loopback --dist-init-addr settings.

Recommended defensive actions

• Verify SGLang deployments for exposure, especially with data-parallel attention enabled and non-loopback --dist-init-addr settings
• Assess the impact of disabling SGLANG_USE_PICKLE_IPC and verify if alternative mitigations are necessary
• Monitor for potential exploitation attempts and update SGLang to a version that addresses this vulnerability
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Review compensating controls for exposed systems while remediation is scheduled and verified

Evidence notes

The CVE record indicates an arbitrary code execution vulnerability in SGLang due to the ZMQ message decoder unconditionally deserializing PickleWrapper payloads via pickle.loads() in _maybe_unwrap_pickle without type allowlisting or authentication.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.