AIKIDO-2026-237045
sglang is vulnerable to Allocation of Resources Without Limits or Throttling
59
Medium Risk
This Affects:
sglangTL;DR
In prefill/decode disaggregation deployments, handle_staging_req() does not validate the chunk_idx field carried in ZMQ STAGING_REQ frames. A peer with access to the decode engine's internal ZMQ rank port can send a frame with an extremely large chunk_idx value. This drives unbounded memory allocation in the scheduler until the process runs out of memory and terminates.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you run SGLang in prefill/decode disaggregation mode with the decode engine's internal ZMQ rank port reachable by untrusted peers.
Background info
sglang is vulnerable to Allocation of Resources Without Limits or Throttling in versions 0.0.1 - 0.5.20.
How to fix this
Upgrade the sglang library to the patch version.
Links
CVE Detail
Related Issue
Other
github.com/sgl-project/sglanggithub.com/sgl-project/sglang/blob/v0.5.20/python/sglang/srt/disaggregation/common/conn.py#L1636-L1640github.com/sgl-project/sglang/blob/v0.5.20/python/sglang/srt/disaggregation/common/staging_handler.py#L781github.com/sgl-project/sglang/blob/v0.5.20/python/sglang/srt/disaggregation/common/staging_handler.py#L848-L860
vulncheck.com/advisories/sglang-through-0.5.20-unbounded-memory-allocation-via-staging-req-chunk-idx
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.