CVE-2026-125263 · Runtime
NO FIX YET · SEE WHAT TO DO
FFmpeg 9.0 through 9.0.2 built with liblcevc_dec does not check LCEVC enhanced output dimensions against max_pixels before allocating frames. A crafted H.264, HEVC or VVC stream declaring a huge LCEVC resolution can force oversized buffer allocations and exhaust memory.
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 9.0 through 9.0.2 compiled with liblcevc_dec are affected. Systems that decode untrusted media files or streams with such a build are the ones to look at; systems that only process trusted media or use other FFmpeg builds can skip it.
Not affected if default-config, trusted-input-only
Who cares ffmpeg, media-processing, video-transcoding
ffmpeg -version and check whether the version is 9.0 through 9.0.2.ffmpeg -decoders | grep -i lcevc.9.0.2 that is named in the patch linked from the NVD entry; the exact fixed version is unknown from the sources.FFmpeg 9.0 through 9.0.2 built with liblcevc_dec fails to validate LCEVC enhanced output dimensions against max_pixels in libavcodec/decode.c before frame allocation. Attackers can supply crafted H.264, HEVC or VVC streams declaring huge LCEVC resolutions to force oversized get_buffer2() allocations and exhaust memory.
This page as .md · .json · CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/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.