FFmpeg through 9.0.2 Heap Buffer Overflow via hap_parse_frame_header()
Affects FFmpeg through 9.0.2 on 32-bit builds when handling Hap video frames with Snappy-compressed chunks and crafted length prefixes. No vendor rating or 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
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects 32-bit builds Hap frames with Snappy-compressed chunks and crafted length prefixes
- 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? →
- 12/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 an integer overflow vulnerability in hap_parse_frame_header() in libavcodec/hapdec.c that allows attackers to trigger a heap buffer overflow on 32-bit builds. Attackers can craft Hap video frames with Snappy length prefixes that wrap tex_size, causing decompress_chunks_thread() to write outside tex_buf and crash the application or potentially execute code.
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 patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects 32-bit builds Hap frames with Snappy-compressed chunks and crafted length prefixesApply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- FFmpeg FFmpeg
through 9.0.2
Evidence 5
- Patch
- 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-125222
Is CVE-2026-125222 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 flaw in hap_parse_frame_header() can let a crafted Hap video frame cause a heap buffer overflow, writing past the bounds of a heap buffer. The advisory says this can crash the application or potentially execute code.Source: vulncheck.com
Which versions are affected by CVE-2026-125222?
FFmpeg: through 9.0.2.Source: cve.now feed data
Am I affected, and how do I check?
The affected range starts at version 0 and runs through FFmpeg 9.0.2, and the issue is stated for 32-bit builds handling Hap frames with Snappy-compressed chunks. To check, run ffmpeg -version to see the version and confirm whether the build is 32-bit.Source: vulncheck.com
How do I fix CVE-2026-125222?
The checked facts do not list a fixed version or an upgrade target. Check the FFmpeg project's release notes or the advisory for a patched release before deciding what to install.Source: vulncheck.com