FFmpeg through 9.0.2 Heap Buffer Overflow via HEVC DXVA Tile Parameters
FFmpeg through 9.0.2 is exposed on Windows when hardware decoding uses DXVA2, D3D11VA, or D3D12VA with HEVC streams that have many non-uniformly spaced tiles. No fixed version 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. Windows system using DXVA2, D3D11VA, or D3D12VA hardware decoding HEVC bitstream with many non-uniformly spaced tiles
- 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 ff_dxva2_hevc_fill_picture_parameters() that allows attackers to corrupt memory via unbounded non-uniform tile counts. Attackers can supply crafted HEVC bitstreams with many non-uniformly spaced tiles to write controlled 16-bit values past fixed-size DXVA arrays during DXVA2, D3D11VA, or D3D12VA decoding on Windows.
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.
Windows system using DXVA2, D3D11VA, or D3D12VA hardware decoding HEVC bitstream with many non-uniformly spaced tilesWorkaround: The checked facts list no vendor workaround. Limiting the affected feature means turning off DXVA2, D3D11VA, and D3D12VA hardware decoding for HEVC on Windows, which removes the code path named in the conditions.
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-125239
Is CVE-2026-125239 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 occurs when crafted HEVC bitstreams with many non-uniformly spaced tiles cause FFmpeg to write controlled 16-bit values past fixed-size DXVA arrays, corrupting memory.Source: vulncheck.com
Which versions are affected by CVE-2026-125239?
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, on Windows systems using DXVA2, D3D11VA, or D3D12VA hardware decoding. A reader can check the installed version with ffmpeg -version and whether a hardware decoding method is in use with the -hwaccel option or ffmpeg -hwaccels.Source: vulncheck.com
How do I fix CVE-2026-125239?
The checked facts name no fixed release, so no upgrade target can be given from them. Check the FFmpeg project for a version later than 9.0.2 that addresses this issue.Source: vulncheck.com
What if there's no patch?
The checked facts list no vendor workaround. Limiting the affected feature means turning off DXVA2, D3D11VA, and D3D12VA hardware decoding for HEVC on Windows, which removes the code path named in the conditions.Source: vulncheck.com