CVE-2026-93088

9.8

SGLang · SGLang

SGLang's multimodal generation runtime is vulnerable to unauthenticated arbitrary code execution via insecure deserialization of ZeroMQ messages in the disaggregated-diffusion orchestrator.

Executive summary

SGLang is vulnerable to unauthenticated remote code execution, posing a critical risk of total system compromise due to insecure deserialization.

Vulnerability

The application utilizes an unauthenticated ZeroMQ ROUTER socket that processes incoming multipart messages using the insecure pickle.loads function without validation. This allows an unauthenticated attacker to trigger arbitrary code execution by sending a crafted payload to the vulnerable endpoint.

Business impact

The vulnerability allows for full remote code execution, which grants an attacker complete control over the affected server. This level of access facilitates data theft, lateral movement within the network, and potential disruption of critical business services. Given the CVSS score of 9.8, this flaw represents a maximum severity risk that requires immediate attention to prevent catastrophic impact.

Remediation

Immediate Action: Restrict access to the ZeroMQ interface via network segmentation or firewall rules until a vendor-supplied patch is installed. Monitor vendor channels for the release of an updated version that replaces the insecure pickle deserialization with a safer alternative.

Proactive Monitoring: Review system and application logs for unusual inbound traffic patterns targeting the ZeroMQ port. Monitor for unexpected process creation or unauthorized network connections originating from the SGLang runtime.

Compensating Controls: Deploy a network intrusion detection system to monitor for malicious ZeroMQ traffic. If possible, utilize host-based controls to restrict communication to the orchestrator to known, trusted management IP addresses.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

This vulnerability presents an extreme risk to infrastructure security due to the lack of authentication and the high impact of remote code execution. Organizations running affected versions of SGLang must prioritize immediate isolation of the affected services from public or untrusted network segments. Applying the vendor-provided patch as soon as it becomes available is the only definitive method to eliminate this risk.

More SGLang CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources