FFmpeg through 9.0.2 Heap Buffer Overflow via HEVC VAAPI Tile Arrays
FFmpeg through 9.0.2 is affected when decoding HEVC with VAAPI hardware acceleration. The checked facts list no vendor rating and no fixed version.
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. Affects FFmpeg through 9.0.2 Attacker supplies a crafted HEVC bitstream with a large picture and many tiles Applications decode HEVC with VAAPI hardware acceleration
- 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 vaapi_hevc_start_frame() in libavcodec/vaapi_hevc.c that copies unbounded PPS tile counts into fixed-size arrays. Attackers can supply a crafted HEVC bitstream with a large picture and many tiles to write controlled 16-bit values past heap-allocated hwaccel data, corrupting memory in applications decoding with VAAPI.
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.
Affects FFmpeg through 9.0.2 Attacker supplies a crafted HEVC bitstream with a large picture and many tiles Applications decode HEVC with VAAPI hardware accelerationWorkaround: The checked facts give no workaround. Limiting the affected feature, such as avoiding HEVC decoding through VAAPI hardware acceleration, would remove the affected path.
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-125202
Is CVE-2026-125202 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 lets a crafted HEVC bitstream with a large picture and many tiles write controlled 16-bit values past heap-allocated hardware acceleration data, corrupting memory.Source: vulncheck.com
Which versions are affected by CVE-2026-125202?
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, and the issue concerns applications decoding HEVC with VAAPI hardware acceleration. To check a setup, look at the FFmpeg version reported by ffmpeg -version and whether HEVC decoding uses VAAPI.Source: vulncheck.com
How do I fix CVE-2026-125202?
The checked facts do not name a fixed release, so no upgrade target can be stated from them. Check the FFmpeg project's advisory for a fixed version.Source: vulncheck.com
What if there's no patch?
The checked facts give no workaround. Limiting the affected feature, such as avoiding HEVC decoding through VAAPI hardware acceleration, would remove the affected path.Source: vulncheck.com