Skip to content
CVE-2026-109225: Memory Exhaustion Vulnerability in SGLang

CVE-2026-109225: Memory Exhaustion Vulnerability in SGLang

First seen 12 Oct 2026, 21:30 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 12, 2026 at 21:31 UTC
  • •CVE-2026-109225 affects SGLang versions up to 0.5.21.
  • •Attackers can exploit the vulnerability via oversized file uploads to cause service outages.
  • •No confirmed exploitation urgency has been reported as of now.

On October 12, 2026, CVE-2026-109225 was published, revealing an unbounded memory allocation vulnerability in SGLang versions up to 0.5.21. This flaw allows unauthenticated remote attackers to exhaust memory by uploading oversized files to the /v1/audio/transcriptions endpoint. Attackers can exploit this by sending concurrent large multipart uploads, potentially crashing the HTTP/tokenizer worker and causing denial of service. The vulnerability poses a significant availability risk for internet-facing AI inference services, particularly those that handle audio transcription. The current status indicates that there is no confirmed exploitation urgency as KEV, SSVC, and EPSS data are not provided. Affected services should monitor for unusually large requests and consider restricting access until a patch is available.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-12
CVE-2026-109225 published
SGLang vulnerability disclosed, allowing memory exhaustion via oversized uploads.
Redpacketsecurity

More articles in this cluster (3)

Following this threat?

Track CVE-2026-109225 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (3)

1 / 3

Common questions

What versions of SGLang are affected?
SGLang versions through 0.5.21 are affected by CVE-2026-109225.
What should I do to mitigate this vulnerability?
Restrict access to the transcription endpoint and apply strict upload-size and concurrency limits until a patch is released.
Is there any confirmed exploitation of this vulnerability?
No confirmed exploitation has been reported at this time.