CVE-2026-125100 · Package
NO FIX YET
FFmpeg's OpenEXR decoder miscalculates the tiled block count in decode_frame() in libavcodec/exr.c when handed a crafted tiled image with large dimensions and small tiles. An attacker who supplies such a file can skip decoding and read uninitialized memory or stale frame data.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that run FFmpeg to decode OpenEXR images from untrusted sources, such as upload pipelines, thumbnailers or media services, are exposed. Systems that only process trusted media or do not decode EXR files can skip it. The sources do not name the fixed version.
Not affected if no-exr-decoding, trusted-input-only
Who cares ffmpeg, libavcodec, media-processing
ffmpeg -version and compare against the fixed release named in the product data (unknown if the sources do not give it)ffmpeg -decoders | grep exr)No fix yet, per the sources.
FFmpeg through 9.0.2 contains an integer overflow vulnerability in the OpenEXR decoder's decode_frame() in libavcodec/exr.c that miscalculates the tiled block count. Attackers can supply a crafted tiled OpenEXR image with large dimensions and small tiles to skip decoding and disclose uninitialized memory or stale frame data.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/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.