# CVE-2026-105758 — vllm-project vllm

> As of 2026-10-05, CVE-2026-105758 is a MEDIUM-severity vulnerability in vllm-project vllm, CVSS v3.1 5.3, EPSS 0.3% (21.6th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-105758 as of 2026-10-05; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-05

## What is CVE-2026-105758?

vLLM is an inference and serving engine for large language models. From 0.24.0 until 0.30.0, the Qwen2VLVideoBackend and Qwen3VLVideoBackend classes accept request-level values for the media_io_kwargs.video.max_frames and media_io_kwargs.video.fps fields without enforcing server-side ceilings. An unauthenticated caller can submit these values to the /tokenize endpoint, causing the sampler to decode every frame selected from attacker-controlled video input, consume disproportionate frontend memory, and potentially terminate the API process before scheduling or admission control. The Rust frontend is not affected because it rejects the media_io_kwargs field. This issue is fixed in version 0.30.0.

The record classifies CVE-2026-105758 under weakness class [CWE-770](https://intel.threadlinqs.com/cwe/CWE-770). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 45 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.3 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 21.6% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-05

## Is CVE-2026-105758 being exploited?

It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [vllm-project](https://intel.threadlinqs.com/vendors/vllm-project): vllm

## How to fix CVE-2026-105758

No vendor patch reference has been recorded for CVE-2026-105758 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-105758

No threat campaign in the Threadlinqs corpus currently references CVE-2026-105758, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, FIRST EPSS, NVD. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/vllm-project/vllm/security/advisories/GHSA-x6mc-67gf-chw4)

**Other references**

- [github.com](https://github.com/vllm-project/vllm/pull/56729)
- [github.com (ea723c81c3ea26425cb69503a5d5e90822a04a45)](https://github.com/vllm-project/vllm/commit/ea723c81c3ea26425cb69503a5d5e90822a04a45)
- [github.com (v0.30)](https://github.com/vllm-project/vllm/releases/tag/v0.30.0)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-105758
No Threadlinqs detection currently covers CVE-2026-105758; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
