CVE-2026-125260 · Package
NO FIX YET · SEE WHAT TO DO
FFmpeg's OpenEXR encoder in libavcodec/exrenc.c writes past a heap scanline buffer when frame height grows mid-stream with RLE compression. An attacker who supplies crafted media can corrupt heap memory and crash the application.
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.
Systems that run FFmpeg to encode OpenEXR output from untrusted input, where resolution can change mid-stream. Applications that only process trusted media or never encode EXR can skip it. The sources do not describe the exact entry point beyond encode_scanline_rle().
Not affected if no-exr-encoding, trusted-input-only
Who cares ffmpeg, media-processing, transcoding
ffmpeg -version; the sources say versions through 9.0.2 are affected.-c:v exr with RLE output.FFmpeg through 9.0.2 contains a heap buffer overflow vulnerability in libavcodec/exrenc.c that allows attackers to corrupt heap memory when encode_scanline_rle() processes frames taller than the encoder height. Attackers can supply crafted input whose resolution grows mid-stream, transcoded to OpenEXR with RLE compression, to write pointers past the scanline array and crash the application.
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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
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.