FFmpeg through 9.0.2 Heap Buffer Overflow via HEVC VDPAU Tile Arrays
Affects FFmpeg through 9.0.2 in applications that use VDPAU hardware decoding for HEVC content. No vendor rating or fix is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Application uses VDPAU hardware decoding for HEVC content Crafted HEVC bitstream with excessive tile columns or rows is decoded
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
FFmpeg through 9.0.2 contains a heap buffer overflow vulnerability in vdpau_hevc_start_frame() in libavcodec/vdpau_hevc.c that copies unbounded PPS tile counts into fixed-size VDPAU arrays. Attackers can supply crafted HEVC bitstreams with excessive tile columns or rows to write controlled 16-bit values past heap-allocated hwaccel data, corrupting memory in applications using VDPAU decoding.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.3/10CVSS 7.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Application uses VDPAU hardware decoding for HEVC content Crafted HEVC bitstream with excessive tile columns or rows is decodedWorkaround: The checked facts list no fix. Until one is available, avoid VDPAU hardware decoding for HEVC content, which removes the vulnerable path, and avoid decoding HEVC bitstreams from untrusted sources.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- FFmpeg FFmpeg
through 9.0.2
Evidence 4
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125219
Is CVE-2026-125219 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A heap buffer overflow in FFmpeg's HEVC VDPAU decoding lets a crafted bitstream with excessive tile columns or rows write controlled 16-bit values past heap-allocated hwaccel data, corrupting memory.Source: vulncheck.com
Which versions are affected by CVE-2026-125219?
FFmpeg: through 9.0.2.Source: cve.now feed data
Am I affected, and how do I check?
FFmpeg versions through 9.0.2 are listed as affected, but only when an application uses VDPAU hardware decoding for HEVC content and decodes a crafted HEVC bitstream with excessive tile columns or rows. Check the installed version with ffmpeg -version and check whether the application's configuration enables VDPAU hardware decoding for HEVC.Source: vulncheck.com
How do I fix CVE-2026-125219?
The checked facts do not list a fixed version, so no specific upgrade target can be given from them. Check the FFmpeg project for a release newer than 9.0.2 that addresses this issue.Source: vulncheck.com
What if there's no patch?
The checked facts list no fix. Until one is available, avoid VDPAU hardware decoding for HEVC content, which removes the vulnerable path, and avoid decoding HEVC bitstreams from untrusted sources.Source: vulncheck.com