CVE-2026-109228
SGLang through 0.5.21 contains a resource budget bypass …
SGLang through 0.5.21 contains a resource budget bypass vulnerability that allows remote attackers to override GLM-V video processing limits by supplying fps, max_frames, max_tokens_per_frame and max_image_tokens in the video_url object. Attackers can set these values arbitrarily high so glm4v.py decodes every frame of high-resolution video at full size, exhausting worker memory and denying service.
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.21/python/sglang/srt/entrypoints/openai/protocol.p
- github.com/sgl-project/sglang/blob/v0.5.21/python/sglang/srt/multimodal/processors/glm4v.p
- github.com/sgl-project/sglang/blob/v0.5.21/python/sglang/srt/multimodal/processors/glm4v.p
- github.com/sgl-project/sglang/blob/v0.5.21/python/sglang/srt/parser/conversation.py#L691
- github.com/sgl-project/sglang/issues/43705
- www.vulncheck.com/advisories/sglang-through-0.5.21-resource-budget-bypass-via-glm-v-video-
- nvd.nist.gov/vuln/detail/CVE-2026-109228
- cve.org/CVERecord?id=CVE-2026-109228
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.