---
title: "CVE-2026-109228: SGLang - Denial of Service"
description: "SGLang through 0.5.21 contains a denial of service caused by resource budget bypass via manipulation of fps, max_frames, max_tokens_per_frame, and max_image_tokens in video_url, letting remote attackers exhaust worker memory, exploit requires crafted video_url parameters."
url: https://panop.io/threat-heartbeat/CVE-2026-109228/
---

# CVE-2026-109228 SGLang - Denial of Service

SGLang through 0.5.21 contains a denial of service caused by resource budget bypass via manipulation of fps, max\_frames, max\_tokens\_per\_frame, and max\_image\_tokens in video\_url, letting remote attackers exhaust worker memory, exploit requires crafted video\_url parameters.

CVSS base score 7.5 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.49% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-109228)

## Details

Type

Denial of Service

Impact

Denial Of Service

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Published

12 October 2026

Updated

15 October 2026

Weakness

[CWE-770](https://cwe.mitre.org/data/definitions/770.html)

## Vendor fix

Update to the latest version beyond 0.5.21.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-109228](https://nvd.nist.gov/vuln/detail/CVE-2026-109228)
- [https://github.com/sgl-project/sglang/blob/v0.5.21/python/sglang/srt/parser/conversation.py#L691](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://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](https://www.vulncheck.com/advisories/sglang-through-0.5.21-resource-budget-bypass-via-glm-v-video-parameters)
- [https://github.com/sgl-project/sglang](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/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#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/multimodal/processors/glm4v.py#L400)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)