FFMPEG · CVE-2026-125222 · Runtime
NO FIX YET · SEE WHAT TO DO
FFmpeg's Hap video decoder miscalculates buffer sizes from crafted Snappy length prefixes, so a malicious Hap file can overflow a heap buffer. An attacker gets a crash or possibly code execution when FFmpeg decodes the file.
first public Nov 9, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
FFmpeg builds through 9.0.2 on 32-bit systems are affected, according to the sources. Services that decode untrusted Hap video files, such as media converters or upload pipelines, are the systems to look at. 64-bit builds and teams that never decode Hap files can likely skip it, though the sources do not state this directly.
Not affected if 64-bit-build, no-hap-decoding
Who cares 32-bit, ffmpeg, media-processing
ffmpeg -version: releases through 9.0.2 are listed as affected.file $(which ffmpeg) or ffmpeg -version configuration line (i386/armhf/x86 targets). The sources describe the overflow on 32-bit builds.ffmpeg -decoders lists hap and whether untrusted video reaches it.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.
This page as .md · .json · CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
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.
9.0.2)