CVE-2026-34379: Memory Corruption in OpenEXR 3.2.0-3.4.9

An attacker could exploit this vulnerability by crafting a malicious EXR file containing a specially crafted DWA or DWAB-compressed FLOAT-type channel. When OpenEXR attempts to decode this file, the misaligned memory write could lead to arbitrary code execution. The impact is significant, as an attacker could potentially gain control of the system processing the malicious image. This could involve data theft, system compromise, or further exploitation of other vulnerabilities on the affected system. The vulnerability’s impact is amplified in environments where EXR files are frequently processed, such as motion picture production pipelines or image processing applications.

1. Reserved2026-03-27
2. Published2026-04-06
3. Modified2026-04-07
4. EPSS updated2026-04-14

The primary mitigation for CVE-2026-34379 is to upgrade to OpenEXR version 3.2.7 or later. If upgrading is not immediately feasible, consider implementing input validation to reject EXR files with suspicious DWA or DWAB compression or FLOAT-type channels. While not a complete solution, this can reduce the attack surface. Additionally, monitor system logs for unusual memory access patterns or crashes related to OpenEXR. There are no specific WAF rules or detection signatures readily available, so focusing on patching is crucial. After upgrading, confirm the fix by attempting to decode a known malicious EXR file (if available) or by running a thorough system scan.