Back to CVE records
Critical 9.1Published May 7, 2026

CVE-2026-42216OpenEXR 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 versions 3.0.0 to before 3.2.9, 3.3.0 to before 3.3.11, and 3.4.0 to before 3.4.11, IDManifest::init() reconstructs strings from a prefix-compressed representation. If the previous string is longer than 255 bytes, the next string is expected to begin with a 2-byte prefix length. The code reads stringList[i][0] and stringList[i][1] without checking that the current string has at least two bytes. This issue has been patched in versions 3.2.9, 3.3.11, and 3.4.11.

CVSS
9.1 CRITICAL (v3.1, NVD)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Weakness (CWE)
CWE-125, CWE-130
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.0.0 before 3.2.9; from 3.3.0 before 3.3.11; from 3.4.0 before 3.4.11
NVD

References

  • exploit, mitigation, 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.