CVE-2026-100650 vLLM before 0.29.0 Resource Exhaustion via Unbounded Media Materialization

High 7.1 Published Updated

Remote attackers can exhaust server memory and bandwidth by sending large media payloads before size limits are enforced, causing denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-100650?

CVE-2026-100650 is a high-severity denial of service vulnerability in Vllm Vllm, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

vLLM through 0.29.0 fetches and fully materializes remote or inline media before enforcing its documented media controls (the VLLM_MAX_AUDIO_CLIP_FILESIZE_MB compressed-audio size cap, default 25 MB, and the per-modality --limit-mm-per-prompt item limits). Across four ingress paths — the shared media-acquisition layer (HTTPConnection.get_bytes()/async_get_bytes()), the chat completions audio_url/base64 path, the batch speech runner, and the Rust frontend POST /tokenize route — the server reads the entire HTTP response body, base64-decodes the inline payload, or spawns one fetch/decode task per media part, and only then applies the limit (or, on some paths, never applies it). A remote attacker can therefore cause the API server or batch-runner process to allocate memory and consume outbound bandwidth proportional to an attacker-chosen body size or media item count before the request is rejected, resulting in pre-inference memory and bandwidth exhaustion (denial of service). The chat and batch surfaces require an API key when one is configured; the Rust frontend /tokenize route is unauthenticated by design. There is no code execution or data disclosure impact.

Weakness: CWE-400

Which versions are affected by CVE-2026-100650?

1 open source package ship an affected version, including vllm. It affects 1 product.

PackageAffectedFixed in
vllm PyPIAll versions0.30.0

Products include Vllm Vllm.

How do I fix CVE-2026-100650?

Upgrade vllm to 0.30.0 or later.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-100650 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100650 exists.

All Vllm Vllm vulnerabilities

Sources

Also known as GHSA-j8gm-f3cq-6c27, GHSA-p6g9-7v3x-m8mv, MINI-2fp9-g6p8-mv7g, MINI-jqmw-rwcg-8jf2, MINI-x36p-25px-ww53, PYSEC-2026-4184.

Is CVE-2026-100650 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free