CVE-2026-125201 · Package
NO FIX YET · SEE WHAT TO DO
FFmpeg's Vulkan AV1 decoder checks the tile-count limit only on entry, so a crafted AV1 stream with more than 256 tiles writes past a heap buffer. An attacker who gets a victim to decode such a file can corrupt heap memory, which may lead to code execution.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only builds of FFmpeg 7.0 before 8.1.3 or 9.x before 9.0.2 that decode AV1 through the Vulkan hardware accelerator are exposed. Services that decode untrusted video uploads with that path are the main concern; software that uses FFmpeg for other codecs or without Vulkan can skip it.
Not affected if no-vulkan-av1-decoding, other-ffmpeg-versions, trusted-input-only
Who cares ffmpeg, libavcodec, video-processing, vulkan
ffmpeg -version and compare against the fixed ranges: 7.0 before 8.1.3 and 9.x before 9.0.2.8.1.3.9.0.2.FFmpeg 7.0 before 8.1.3 and 9.x before 9.0.2 contains a heap out-of-bounds write vulnerability in vk_av1_decode_slice() in libavcodec/vulkan_av1.c because the tile-count limit is checked only on entry. Attackers can supply a crafted AV1 stream with more than 256 tiles decoded via the Vulkan hardware accelerator to overflow tile_sizes and corrupt heap memory.
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.