CVE-2026-100650Medium· 6.5▾ TwilightPoC availablevLLM 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-p…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 35.8 · likelihood 0.2 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Sep 28.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
0.6%
Exploit / PoC code exists
Last analysed / modified upstream
0.6% → 0.8%
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.
vllm <= 0.29.0Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Affected packages:
vllm < 0.30.0Patched in:
vllm 0.30.0Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-93592High· 7.5vLLM versions before 0.28.0 fail to validate the lower bound of token IDs in the /v1/embeddings and /pooling endpoints, allowing unauthenticated attackers to crash the engine by submitting negative token IDs
CVE-2026-37237High· 7.5vLLM up to and including 0.17.0 allows remote attackers to cause a Denial of Service via memory exhaustion
CVE-2026-105759Medium· 5.9vLLM is an inference and serving engine for large language models
CVE-2026-69147Medium· 6.5vLLM is an inference and serving engine for large language models
CVE-2026-114055High· 7.5vLLM 0.7.3 before 0.31.0 DoS via Unvalidated mm_processor_kwargs
CVE-2026-105760Medium· 5.3vLLM is an inference and serving engine for large language models