CVE-2026-86793
Received Received - Intake

SGLang Unauthenticated Pickle Deserialization Vulnerability

Vulnerability report for CVE-2026-86793, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-11

Last updated on: 2026-09-11

Assigner: CERT/CC

Description

SGLang allows unauthenticated pickle deserialization through /update_weights_from_tensor when no auth keys are configured, and the SafeUnpickler policy can be bypassed because builtins.import and builtins.getattr are resolvable, enabling code execution via pickle REDUCE.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-11
Last Modified
2026-09-11
Generated
2026-09-11
AI Q&A
2026-09-11
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-86793 is a vulnerability in SGLang, an open-source framework for deploying large language models. It allows unauthenticated remote code execution due to a bypass in SGLang's SafeUnpickler, which was meant to prevent deserialization attacks. The flaw exists because SafeUnpickler's allowlist includes 'builtins' and its denylist fails to block dangerous functions like __import__ and getattr. Attackers can exploit this by sending malicious pickle payloads to the unauthenticated /update_weights_from_tensor endpoint.

Detection Guidance

Check if SGLang is running with authentication disabled by inspecting HTTP requests to /update_weights_from_tensor. Monitor for unexpected pickle deserialization attempts or base64-encoded payloads in logs. Use network traffic analysis tools to detect unauthorized access to the vulnerable endpoint.

Impact Analysis

If you use SGLang without authentication enabled, an attacker could remotely execute arbitrary code on your AI servers. This could lead to data theft, server compromise, or disruption of services. The attack requires no authentication and targets a specific HTTP endpoint, making it particularly dangerous for exposed systems.

Mitigation Strategies

Enable authentication for SGLang and restrict access to the /update_weights_from_tensor endpoint. Block or filter requests containing base64-encoded pickle payloads. Update SafeUnpickler to remove 'builtins' from ALLOWED_MODULE_PREFIXES and explicitly block __import__ and getattr in DENY_CLASSES.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-86793. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart