CVE-2026-34545
Openexr remote code execution
- Published1 Apr 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2026-34545
- https://bugzilla.redhat.com/show_bug.cgi?id=2454139
- https://github.com/AcademySoftwareFoundation/openexr/commit/3827998f5c041d6a94c6af24bbb363daa669e4b3
- https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.4.7
- https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-ghfj-fx47-wg97
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34545.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-34545 being actively exploited?
CVE-2026-34545 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.74%.
How severe is CVE-2026-34545?
CVE-2026-34545 has a CVSS 3.1 base score of 7.3, rated high. EPSS estimates a 0.74% probability of exploitation.
Which products are affected by CVE-2026-34545?
Affected products include Openexr.
How do I fix CVE-2026-34545?
Upgrade affected software to a fixed version, for example Openexr 3.4.7 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-34545 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.