FFMPEG · CVE-2026-125259 · Package
NO FIX YET · SEE WHAT TO DO
FFmpeg miscalculates the buffer size for ProRes video encoding when frames are very large, because it uses 32-bit arithmetic. An attacker who supplies a high-resolution video transcoded with the prores_ks encoder can write past an undersized packet buffer and corrupt heap memory.
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 that run FFmpeg to encode ProRes video from user-supplied or untrusted high-resolution input are exposed. Installations that only process trusted local media, or never use the prores_ks encoder, are less exposed. The sources do not state a fixed version; a patch link is listed but its contents were not provided.
Not affected if no-prores-ks-encoding, no-prores_ks-encoding, trusted-input-only
Who cares ffmpeg, heap-overflow, prores, prores_ks, video-transcoding
9.0.2 are listed as affecteds proresenc_kostya_common.c has the Frame too large to encode' checkFFmpeg through 9.0.2 contains an integer overflow vulnerability in ff_prores_kostya_encode_init() that miscalculates frame_size_upper_bound using 32-bit arithmetic for large frame dimensions. Attackers can supply a high-resolution video transcoded with the prores_ks encoder, causing encode_frame() to write slices past an undersized packet buffer and corrupt heap memory.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
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.
9.0.2