CVE-2026-125248: FFmpeg integer overflow in Vulkan FFV1 encoder

CVE-2026-125248 · Severity: high · CVSS 7 · Published 2026-11-09

FFmpeg is a widely-used multimedia framework for processing video and audio. When transcoding large video frames to FFV1 format using the Vulkan GPU encoder in versions 9.0 through 9.0.2, an integer overflow causes the GPU buffer to be undersized, resulting in out-of-bounds memory writes that crash the encoder or corrupt GPU memory.

Technologies: Ffmpeg. Vendors: Ffmpeg.

Quick answers

Is CVE-2026-125248 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-125248 being exploited in the wild.
How severe is CVE-2026-125248?
High severity, with a CVSS score of 7, published 9 November 2026.
Which products and versions are affected?
Ffmpeg 9.0 through 9.0.2.
Is there a fix for CVE-2026-125248?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-125248 attacked?
It is attacked over the network or with local access, in a software library.
Am I affected by CVE-2026-125248?
Check whether you run Ffmpeg 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.

Technical details

An integer overflow in libavcodec/ffv1enc_vulkan.c fails to properly size the float remap GPU buffer for large GBRPF32 or GBRAPF32 frames, causing out-of-bounds writes when processing the remap data. The vulnerability requires the attacker to supply specially crafted large video frames to the Vulkan encoder; no authentication or user interaction beyond providing a malicious file is needed. A successful exploit causes memory corruption or denial of service.

Affected products

  • FFmpeg FFmpeg 9.0 through 9.0.2

Timeline

  • 2026-11-09: disclosed: CVE-2026-125248 published
  • 2026-10-17: other: Fix proposed in pull request #25136

References

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