CVE-2026-105758
Description
A flaw was found in vllm. An unauthenticated remote attacker can cause a Denial of Service (DoS) by sending requests with excessively high video processing parameters to affected API endpoints. Because the backend does not enforce upper bounds on user-controlled video frame counts and rates, the service attempts to decode all frames from attacker-provided video data. This behavior consumes disproportionate server memory and can terminate the API process, making the service unavailable.
Statement
A MODERATE severity flaw was found in vLLM, as shipped in Red Hat AI Inference Server 3 and Red Hat OpenShift AI (RHOAI). 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 upper bounds. An unauthenticated remote attacker can submit requests with excessively high video frame counts or sampling rates to API endpoints such as /tokenize, causing the service to decode every frame selected from attacker-controlled video input. This consumes disproportionate frontend memory and can terminate the API process before scheduling or admission control, resulting in a denial of service with no impact on confidentiality or integrity (CVSS 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, matching the upstream rating). The Rust frontend is not affected because it rejects the media_io_kwargs field. For the affected Red Hat AI Inference Server and RHOAI products the fix is deferred because the impact is MODERATE with a CVSS score below 7.0; the residual risk is limited to availability, where an unauthenticated remote attacker could crash the vLLM API process and make the inference service unavailable until it is restarted.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.