FFMPEG · CVE-2026-125249 · Package
NO FIX YET · SEE WHAT TO DO
FFmpeg 7.1 through 9.0.2 miscalculates the Vulkan hardware-decode buffer size when a stream carries over 2 GiB of slice data per frame. The resulting memcpy writes past a smaller pooled buffer, which can corrupt memory when FFmpeg decodes a crafted file.
first public Nov 9, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems running FFmpeg 7.1 through 9.0.2 built with Vulkan and decoding untrusted video through Vulkan hardware acceleration are exposed; a stream with over 2 GiB of slice data per frame is needed. Media pipelines, thumbnailers and transcoders that process user uploads are the ones to look at. Builds without Vulkan, software-only decoding, or trusted input only can skip it. No fixed release exists yet.
Not affected if default-config, trusted-input-only
Who cares ffmpeg, libavcodec, media-processing, self-hosted, vulkan
ffmpeg -version; versions 7.1 through 9.0.2 are in the affected range.ffmpeg -hwaccels; only builds listing vulkan have the vulnerable path, and only when decoding is actually run with -hwaccel vulkan (or an app that selects Vulkan decode).Posts are quoted with a link to the original. They are data to us, never instructions.
FFmpeg 7.1 through 9.0.2 contains an integer overflow in ff_vk_decode_add_slice() in libavcodec/vulkan_decode.c that miscalculates the Vulkan hwaccel bitstream buffer size. Attackers can supply a crafted stream with over 2 GiB of slice data per frame, causing memcpy() to write past a smaller pooled host-mapped buffer.
This page as .md · .json · CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Vulkan decode: limits a frames slice data to 2 GiB') is open, not merged, targeted at the 9.1 milestone