CVE-2026-93838
SGLang versions through 0.5.20 contain an unbounded memory …
SGLang versions through 0.5.20 contain an unbounded memory allocation vulnerability in handle_staging_req() that fails to validate chunk_idx from ZMQ STAGING_REQ frames in prefill/decode disaggregation deployments. Attackers with access to the decode engine's internal ZMQ rank port can send a frame with an extremely large chunk_idx value, causing the scheduler to allocate memory until the system runs out and terminates the process.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/sgl-project/sglang
- github.com/sgl-project/sglang/blob/v0.5.20/python/sglang/srt/disaggregation/common/conn.py
- github.com/sgl-project/sglang/blob/v0.5.20/python/sglang/srt/disaggregation/common/staging
- github.com/sgl-project/sglang/blob/v0.5.20/python/sglang/srt/disaggregation/common/staging
- github.com/sgl-project/sglang/issues/39764
- www.vulncheck.com/advisories/sglang-through-0.5.20-unbounded-memory-allocation-via-staging
- nvd.nist.gov/vuln/detail/CVE-2026-93838
- cve.org/CVERecord?id=CVE-2026-93838
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.