Resource Exhaustion Affecting vllm-cu130 package, versions <0.29.0-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.65% (50th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-VLLMCU130-20377573
  • published2 Oct 2026
  • disclosed26 Sept 2026

Introduced: 26 Sep 2026

NewCVE-2026-100650  (opens in a new tab)
CWE-400  (opens in a new tab)

How to fix?

Upgrade Minimos:latest vllm-cu130 to version 0.29.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream vllm-cu130 package and not the vllm-cu130 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1