# CVE-2026-109225: SGLang through 0.5.21 Memory Exhaustion DoS via /v1/audio/transcriptions Upload

> Unauthenticated attackers can crash SGLang servers by uploading oversized audio files, causing memory exhaustion and service denial.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-4fxq-6r94-mchm

## What is CVE-2026-109225?

CVE-2026-109225 is a high-severity denial of service vulnerability in sgl-project sglang, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SGLang through 0.5.21 contains an unbounded memory allocation vulnerability that allows unauthenticated remote attackers to exhaust memory by uploading oversized files to /v1/audio/transcriptions. Attackers can send concurrent large multipart uploads, which are fully read into memory before validation, to crash the HTTP/tokenizer worker and deny service.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-109225?


## How do I fix CVE-2026-109225?

No fix has been published for CVE-2026-109225 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109225 being exploited?

There is no known exploitation of CVE-2026-109225 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109225 and fix it if it is affected.

What it is: CVE-2026-109225 is a high-severity denial of service vulnerability in sgl-project sglang, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109225 in the wild and no public exploit code.

Affected product: sgl-project sglang. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109225/ (Markdown: https://insights.sbomify.com/CVE-2026-109225/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109225
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109225
- OSV: https://osv.dev/vulnerability/CVE-2026-109225

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109225/
Summaries are generated and may contain mistakes; the official description above is the record.