CVE-2026-125067 · Package
NO FIX YET
FFmpeg's VBLE video decoder in libavcodec ignores a bit reader setup failure on oversized frames, leaving a NULL buffer that gets read. An attacker who supplies a crafted AVI file can crash the process that decodes it.
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 run FFmpeg's libavcodec to decode AVI files from untrusted sources, such as media upload, transcoding or thumbnail services. Environments that never decode untrusted AVI input are less exposed. The sources do not say whether a non-default build or codec setting is required.
Not affected if no-untrusted-avi-input
Who cares ffmpeg, libavcodec, media-processing
ffmpeg -version, since the description says versions through 9.0.2 are affectedNo fix yet, per the sources.
FFmpeg through 9.0.2 contains a NULL pointer dereference vulnerability in vble_decode_frame() in libavcodec/vble.c because it ignores init_get_bits() failure on oversized packets. Attackers can supply a crafted AVI file with a 268435452-byte VBLE frame, causing reads from a NULL bit reader buffer that crash the process.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/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.
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.