SGLang through 0.5.19 Unbounded Memory Allocation via bootstrap_room
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.7epss 0.4%
exploitation probability
0.4%top 66% of all CVEs
observed exploitation
nono source reports it
SGLang through 0.5.19 in prefill/decode disaggregation mode with Mooncake KV transfer backend fails to validate bootstrap_room values, allowing unbounded transfer state allocation. Unauthenticated attackers can reach the decode engine's POST /generate endpoint and submit arbitrary bootstrap_room values to exhaust prefill process memory until out-of-memory termination.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Affected products
sgl-project · sglangReferences
https://github.com/sgl-project/sglanghttps://github.com/sgl-project/sglang/blob/v0.5.19/python/sglang/srt/disaggregation/mooncake/conn.py#L1988-L1990https://github.com/sgl-project/sglang/blob/v0.5.19/python/sglang/srt/disaggregation/mooncake/conn.py#L2118-L2119https://github.com/sgl-project/sglang/blob/v0.5.19/python/sglang/srt/managers/io_struct.py#L281https://github.com/sgl-project/sglang/blob/v0.5.19/python/sglang/srt/managers/scheduler.py#L2672-L2690https://github.com/sgl-project/sglang/issues/39428https://www.vulncheck.com/advisories/sglang-through-0.5.19-unbounded-memory-allocation-via-bootstrap-room