CVE-2026-109228
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://github.com/sgl-project/sglang
- https://github.com/sgl-project/sglang/blob/v0.5.21/python/sglang/srt/entrypoints/openai/protocol.py#L592-L594
- https://github.com/sgl-project/sglang/blob/v0.5.21/python/sglang/srt/multimodal/processors/glm4v.py#L160-L167
- https://github.com/sgl-project/sglang/blob/v0.5.21/python/sglang/srt/multimodal/processors/glm4v.py#L400
- https://github.com/sgl-project/sglang/blob/v0.5.21/python/sglang/srt/parser/conversation.py#L691
- https://github.com/sgl-project/sglang/issues/43705
- https://www.vulncheck.com/advisories/sglang-through-0.5.21-resource-budget-bypass-via-glm-v-video-parameters
CWEs
CWE-770
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.