CVE-2026-125242 · Runtime
NO FIX YET
FFmpeg's VDPAU decoding code in libavcodec leaks a buffer table when a picture is aborted before end_frame. A crafted H.264 stream with malformed NAL units can repeatedly trigger this, exhausting heap memory and causing a denial of service.
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 H.264 video with FFmpeg and use the VDPAU hardware path are the ones exposed. Services that only process trusted media or do not use VDPAU can likely skip it. The sources do not give a fixed version.
Not affected if trusted-input-only, vdpau-not-used
Who cares ffmpeg, h264, libavcodec, self-hosted, vdpau
ffmpeg -version and compare it against the ranges in the NVD entry.ffmpeg -hwaccels lists vdpau when it is enabled).No fix yet, per the sources.
FFmpeg through 9.0.2 contains a memory leak vulnerability in libavcodec/vdpau.c that allows attackers to exhaust heap memory by aborting pictures before end_frame. Attackers can supply crafted H.264 streams with malformed NAL units that repeatedly abandon pictures, leaking the bitstream_buffers table continuously and causing denial of service.
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
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.