Advisory

PYSEC-2026-4184

Also known as: CVE-2026-100650, GHSA-p6g9-7v3x-m8mv

Summary

The record has no summary.

Details

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.

Severity

Not rated by the source.

Dates

Published
2026-09-26 14:16 UTC
Modified
2026-10-07 10:00 UTC

Affected packages and fixes

vllm

PyPI · All systems

Affected

  • introduced 0, fixed 0.30.0 (ecosystem)

Fixed versions

0.30.0

Fix

  • Fixed version 0.30.0
    pip install --upgrade vllm==0.30.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences