CVE-2026-7301: Critical severity SGLangs SGLangs multimodal generation runtime scheduler vulnerability
SGLangs multimodal generation runtime scheduler's ROUTER socket binds to 0.0.0.0 by default and contains a sink that calls pickle.loads() on incoming messages, enabling RCE when exposed to the internet.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Change the ROUTER socket binding from the default 0.0.0.0 to a non-internet-facing interface so it is not exposed externally.
SGLangs multimodal generation runtime scheduler ROUTER socket bind address = bind only to a non-public interface (not 0.0.0.0) - Compensating control
Restrict network access so the SGLangs multimodal generation runtime scheduler’s ROUTER socket is not reachable from the internet (e.g., block inbound traffic at the firewall/ACL and allow only trusted internal hosts).
- Operational
Restart the SGLangs service after changing the ROUTER socket bind configuration and ensure the scheduler is not exposed externally during restart.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-7301?
CVE-2026-7301 has a high severity rating due to its potential for remote code execution when exploited.
How do I fix CVE-2026-7301?
To fix CVE-2026-7301, bind the ROUTER socket to a specific IP address instead of 0.0.0.0 and avoid using pickle.loads() on untrusted data.
What are the potential consequences of CVE-2026-7301?
Exploiting CVE-2026-7301 can lead to remote code execution on the affected system, compromising its security.
Is CVE-2026-7301 present in all versions of the SGLangs multimodal generation runtime scheduler?
CVE-2026-7301 affects the SGLangs multimodal generation runtime scheduler by default settings but may vary based on specific configurations.
Can CVE-2026-7301 be exploited without network access?
No, CVE-2026-7301 requires internet exposure for exploitation due to its socket binding behavior.