CVE-2026-34545: OpenEXR: integer overflow lead to OOB in HTJ2K decoder
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From version 3.4.0 to before version 3.4.7, an attacker providing a crafted .exr file with HTJ2K compression and a channel width of 32768 can write controlled data beyond the output heap buffer in any application that decodes EXR images. The write primitive is 2 bytes per overflow iteration or 4 bytes (by another path), repeating for each additional pixel past the overflow point. In this context, a heap write overflow can lead to remote code execution on systems. This issue has been patched in version 3.4.7.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenEXRto a version that resolves this vulnerability.Fixed in 3.4.7
Event History
Frequently Asked Questions
What is the severity of CVE-2026-34545?
CVE-2026-34545 has a high severity rating of 8.4.
What is the nature of the vulnerability in CVE-2026-34545?
CVE-2026-34545 is caused by an integer overflow that leads to an out-of-bounds write in the HTJ2K decoder of OpenEXR.
How do I fix CVE-2026-34545?
To fix CVE-2026-34545, upgrade OpenEXR to version 3.4.7 or later.
Which versions of OpenEXR are affected by CVE-2026-34545?
Versions of OpenEXR from 3.4.0 to before 3.4.7 are affected by CVE-2026-34545.
What could an attacker achieve by exploiting CVE-2026-34545?
An attacker could potentially execute arbitrary code by providing a specially crafted .exr file that exploits the vulnerability in CVE-2026-34545.