CVE-2026-125244 · Package
NO FIX YET · SEE WHAT TO DO
FFmpeg's VVC (H.266) decoder writes past the end of a buffer when a crafted bitstream declares too many tile or WPP entry points. An attacker who supplies such a video file can corrupt decoder 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.
Systems that decode untrusted VVC/H.266 video with FFmpeg, such as media transcoding services, thumbnailers or upload pipelines. Applications that never decode VVC, or only process trusted media, are unlikely to be reachable.
Not affected if no-vvc-decoding, trusted-input-only
Who cares ffmpeg, libavcodec, media-processing, self-hosted
ffmpeg -version and compare against the fixed versions below.ffmpeg -decoders | grep -i vvc).8.1.3 or later on the 8.x line9.0.2 or later on the 9.x lineFFmpeg before 8.1.3 and 9.x before 9.0.2 contains an out-of-bounds write vulnerability in the VVC decoder's sh_entry_points() function in libavcodec/vvc/ps.c. Attackers can supply a crafted VVC (H.266) bitstream whose SPS/PPS tile and WPP layout produces excess entry points, overflowing entry_point_start_ctu and corrupting decoder 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.
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.