Is CVE-2026-22778 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-22778 being exploited in the wild.

How severe is CVE-2026-22778?

Critical severity, with a CVSS score of 9.8, published 2 February 2026.

Which products and versions are affected?

Ffmpeg 4.x; OpenCV 4.x; vllm (PyPI) ECOSYSTEM:introduced=0.8.3,fixed=0.14.1.

Is there a fix for CVE-2026-22778?

Yes. vllm (PyPI): upgrade to 0.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-22778 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-22778?

Check whether you run Ffmpeg, OpenCV, vllm (PyPI) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-22778: vLLM remote code execution via JPEG2000 heap overflow and ASLR bypass

CVE-2026-22778 · Severity: critical · CVSS 9.8 · Published 2026-02-02

vLLM, a popular library for serving artificial intelligence models, is vulnerable to a critical security flaw when processing video content. An attacker can send a specially crafted video URL to the server, which allows them to take complete control of the system and execute unauthorized commands. This could lead to the theft of sensitive AI models, customer data, or a total service outage.

Technologies: Ffmpeg, OpenCV, vllm (PyPI), Vllm. Vendors: Ffmpeg, OpenCV, PyPI, Vllm.

Quick answers

Is CVE-2026-22778 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-22778 being exploited in the wild.
How severe is CVE-2026-22778?: Critical severity, with a CVSS score of 9.8, published 2 February 2026.
Which products and versions are affected?: Ffmpeg 4.x; OpenCV 4.x; vllm (PyPI) ECOSYSTEM:introduced=0.8.3,fixed=0.14.1.
Is there a fix for CVE-2026-22778?: Yes. vllm (PyPI): upgrade to 0.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-22778 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-22778?: Check whether you run Ffmpeg, OpenCV, vllm (PyPI) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

vllm (PyPI): upgrade to 0.14.1 or later
```
pip install "vllm>=0.14.1"
```

Technical details

A remote code execution (RCE) vulnerability exists in vLLM due to a chain of two flaws. First, an information leak in PIL error messages exposes heap memory addresses, allowing attackers to bypass Address Space Layout Randomization (ASLR). Second, a heap buffer overflow exists in the JPEG2000 decoder (libopenjp2) within the FFmpeg 5.1.x bundle used by OpenCV (cv2), which vLLM utilizes for video decoding. By providing a malicious video URL containing a JPEG2000 'cdef' box that remaps color channels (e.g., Y to U), an attacker can trigger an overflow to overwrite function pointers (such as AVBuffer.free) with system calls. This exploit can be triggered via the /v1/chat/completions or /v1/invocations endpoints on deployments serving video models. The issue is resolved in vLLM version 0.14.1.

Affected products

vLLM Project vLLM >= 0.8.3, < 0.14.1
OpenCV OpenCV (cv2) with FFmpeg bundle 4.x

Identifiers

CVE-2026-22778
GHSA-4r2x-xpjr-7cvv
PYSEC-2026-565

Timeline

2026-02-02: advisory: GHSA-4r2x-xpjr-7cvv published
2026-02-02: patched: vLLM version 0.14.1 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.