CVE-2026-69147

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

vLLM is an inference and serving engine for large language models. Prior to 0.28.0, request bodies for Chat Completions and Responses can set media_io_kwargs.video.video_backend to pynvvideocodec, and MediaConnector.fetch_video forwards that choice to VideoMediaIO even when startup configuration selected a software decoder. The engine's _reserve_mm_ipc_gpu_memory logic budgets decoder memory only from static configuration, so the request-selected VIDEO_LOADER_REGISTRY backend can create a CUDA context, decoder surfaces, and decoded-frame allocations that were not removed from the engine's KV-cache budget. An attacker able to submit video requests to a video-capable GPU deployment with PyNvVideoCodec installed can exhaust shared GPU memory, causing request failures, worker crashes, or denial of service. The first release containing the fix is version 0.28.0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
github_commit

commit ba22152096b2 (vllm-project/vllm)

Fix landed in vllm-project/vllm commit ba22152096b2 — awaiting tagged release

https://github.com/vllm-project/vllm/commit/ba22152096b2484faa3579624a253d54804d876d
github_commit

commit 283893c72292 (vllm-project/vllm)

Fix landed in vllm-project/vllm commit 283893c72292 — awaiting tagged release

https://github.com/vllm-project/vllm/commit/283893c72292ede38d277e3cd2b9b64c3e4f1dda
github_pr

fix(security): block request-level GPU video backend selection withou…

Fix merged in vllm-project/vllm PR #47259 on 2026-07-06 — awaiting tagged release

https://github.com/vllm-project/vllm/pull/47259
github Patch Available🟡 PoC Available

Request-selected PyNvVideoCodec GPU decode bypasses static VRAM reservation · Advisory · vllm-project/vllm · GitHub

https://github.com/vllm-project/vllm/security/advisories/GHSA-8pw2-6jv3-mj5j

Vendor Advisories for CVE-2026-69147(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 12:58 UTCEG score recompute
  3. 2026-09-19 14:43 UTCEG score recompute
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 16:31 UTCEG score recompute
  6. 2026-09-17 18:18 UTCEG score recompute
  7. 2026-09-16 19:24 UTCEG score recompute
  8. 2026-09-16 18:52 UTCEG score recompute
  9. 2026-09-16 18:24 UTCEG score recompute
  10. 2026-09-16 18:00 UTCEG score recompute
  11. 2026-09-16 17:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-69147?
CVE-2026-69147 is a medium vulnerability published on September 16, 2026. vLLM is an inference and serving engine for large language models. Prior to 0.28.0, request bodies for Chat Completions and Responses can set mediaiokwargs.video.videobackend to pynvvideocodec, and MediaConnector.fetchvideo forwards that choice to VideoMediaIO even when startup configuration…
When was CVE-2026-69147 disclosed?
CVE-2026-69147 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69147 actively exploited?
CVE-2026-69147 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.9% of all scored CVEs.
What is the CVSS score of CVE-2026-69147?
CVE-2026-69147 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-69147?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69147, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-69147

Explore →

Is Your Infrastructure Affected by CVE-2026-69147?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs