Skip to main content
VulnerabilityPublished Updated

CVE-2026-105758: vllm · Unthrottled Resource Allocation

Affects vllmSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.30.0 when convenient.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.30.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade vllm to 0.30.0.

Affected software

ProductAffectedFixed in
vllm-projectvllmAffected
  • >=0.24.0 <0.30.0
Fixed in
  • 0.30.0
PyPIvllmpkg:pypi/vllmOther threatsAffected
  • >=0.24.0 <0.30.0
Fixed in
  • 0.30.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade vllm to version 0.30.0 or later, where this vulnerability is fixed by enforcing server-side limits on media_io_kwargs.video.max_frames and media_io_kwargs.video.fps. Until upgrade, consider restricting access to the /tokenize endpoint or implementing rate limiting to mitigate exploitation.

Description

CVE-2026-105758 is a resource allocation vulnerability in vllm versions 0.24.0 through 0.29.999 that allows unauthenticated attackers to submit excessive video frame and frame rate values to the /tokenize endpoint. This can cause disproportionate memory consumption and potentially terminate the API process. The issue is fixed in version 0.30.0.

References

Community reviews

Loading reviews…