Servers and applications
CVE-2026-69147
Request-selected PyNvVideoCodec GPU decode bypasses static VRAM reservation
- Severity
- Medium 6.5
- Published
- 28 Aug 2026
- Last changed
- 7 Oct 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 0.28.0
- Exploit chance
- 0.6% in the next 30 daysHigher than 48% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H- Also known as
- GHSA-8pw2-6jv3-mj5j
- Sources
- NVD, Project advisories (GitHub)
Description
Current vLLM main lets an inference request choose the PyNvVideoCodec GPU video decoder through media_io_kwargs.video.video_backend, but engine GPU memory reservation is computed only from static startup configuration and VLLM_VIDEO_LOADER_BACKEND. If the server starts with the default OpenCV/software backend and no --mm-ipc-gpu-memory-gb budget, a client can still route a video request into the PyNvVideoCodec path after startup, causing frontend CUDA-context, decoder-surface, and decoded-frame GPU allocations that were not carved out of the engine KV-cache budget.
The vulnerable boundary is the split between request-time media decoding choices in the API server and startup-time memory budgeting in the engine worker. Request bodies for Chat Completions and Responses expose media_io_kwargs, and those values are forwarded to the shared media connector.
Affected software
| Software | Affected versions |
|---|---|
vLLMServers and applications · cpe:a:vllm:vllm |
|
vLLMServers and applications · github:vllm-project/vllm |
|
About vLLM
open-source software for large language model inference
- Docker Hub pulls
- 44,195,225Docker Hub, 15 Nov 2026
- GitHub stars
- 96,943GitHub, 15 Nov 2026
- Forks
- 24,836GitHub, 15 Nov 2026
- Latest release
- v0.33.0rc3GitHub, 15 Nov 2026
- Released
- 2 Nov 2026GitHub
- License
- Apache Software License 2.0Wikidata
- First published on GitHub
- 9 Feb 2023GitHub
Website Source code Docker image
Vulnerabilities in vLLM
- In our list
- 169
- Published in the last 12 months
- 150
- Critical, last 12 months
- 6
- High, last 12 months
- 63
- Known exploited
- 0
- CVE-2026-130686vLLM 0.6.0 before 0.33.0 Resource Exhaustion via Multi-Image RequestsHigh 8.7 18 Nov 2026
- CVE-2026-130684vLLM before 0.33.0 Path Traversal via speculators_config verifier.name_or_pathMedium 5.3 18 Nov 2026
- CVE-2026-130685vLLM 0.28.0 before 0.33.0 Unauthenticated DoS via Out-of-Range Prompt Token IDHigh 8.7 18 Nov 2026
- GHSA-xgh8-qwjh-q853/v1/systemone bypasses the --trust-request-chat-template gateMedium 6.5 18 Nov 2026
- CVE-2026-129356vllm-project vllm Common Prefix single_type_kv_cache_manager.py race conditionLow 2.3 15 Nov 2026
- CVE-2026-126394vLLM 0.30.0 before 0.31.0 Resource Exhaustion via OpenPangu Video Backend num_framesMedium 6.9 13 Nov 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-69147
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-69147
- GitHub Advisory Database https://github.com/advisories/GHSA-8pw2-6jv3-mj5j
- github.com https://github.com/vllm-project/vllm/security/advisories/GHSA-8pw2-6jv3-mj5j