FFMPEG · CVE-2026-125262 · Runtime
NO FIX YET · SEE WHAT TO DO
FFmpeg through 9.0.2 fails to check LCEVC output picture dimensions against the allocated frame in libavcodec/lcevcdec.c. A crafted H.264 or HEVC stream carrying LCEVC enhancement data can corrupt heap memory in a decoding application.
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.
FFmpeg 7.1 through 9.0.2 (VulnCheck) builds that decode H.264 or HEVC video carrying LCEVC enhancement data, such as upload, transcoding or thumbnailing services handling untrusted video. The LCEVC path appears to need the optional lcevc_dec library; builds without it are probably not affected, but the sources do not confirm the default. Systems that only handle trusted media can skip it.
Not affected if no-liblcevc-dec, trusted-input-only
Who cares ffmpeg, lcevc, libavcodec, video-processing
4.2.0FFmpeg through 9.0.2 contains a heap buffer overflow vulnerability in libavcodec/lcevcdec.c because LCEVC output picture dimensions are not validated against the allocated frame. Attackers can embed crafted LCEVC enhancement data with differing global configurations in H.264 or HEVC streams to corrupt heap memory in decoding applications.
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.