Back to CVE records
High 7.3Published Apr 1, 2026

CVE-2026-34545OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry.

Updated under an hour ago ()

Does this affect you?

It affects openexr. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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
7.3 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-122, CWE-190, CWE-1284
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Not given
NVD analysis
Modified
Record last updated
Jul 15, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
openexr openexr
openexr:openexr
from 3.4.0 before 3.4.7
NVD

References

  • patch
  • product, release-notes
  • exploit, vendor-advisory

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.