Advisory record · GHSA-4r2x-xpjr-7cvv

vLLM has RCE In Video Processing

CVSS 9.8 CriticalCriticalEPSS 0.18 · 97th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.
  • CVSS score 9.8 (7.0 or more) and EPSS 0.18 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 2 Feb 2026, 17:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
vllmPyPI>=0.8.3, <0.14.10.14.1
Identifiers
GHSA-4r2x-xpjr-7cvv · CVE-2026-22778 · PYSEC-2026-565
Weakness (CWE)
CWE-122 · CWE-209 · CWE-532
Published
2 Feb 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of vllm from 0.8.3 before 0.14.1 are affected when serving a video model. An unauthenticated attacker can send a request with a malicious video URL, and a chain of an information leak and a JPEG2000 heap overflow in the video decoding stack can lead to arbitrary command execution on the server. Upgrade vllm to 0.14.1 or later; deployments not serving a video model are not affected.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.18, the 97th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.