Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.

OpenEXR: Memory Corruption Risk in Image Files

published 5 months ago
Summary

OpenEXR is a software used to create and edit high-dynamic-range image files. A security update is available to prevent memory corruption that could allow attackers to execute malicious code. Update to version 3.2.9, 3.3.11, or 3.4.11 to fix this issue.

What to do
  • Update openeuler openexr to version 3.1.11-9.oe2403.
Affected software
Ecosystem VendorProductAffected versions
openEuler:24.03-LTS openeuler openexr < 3.1.11-9.oe2403
Fix: upgrade to 3.1.11-9.oe2403
Original advisory text
OpenEXR security update
OpenEXR is a high dynamic-range (HDR) image file format originally developed by Industrial Light &amp;amp; Magic for use in computer imaging applications.

Security Fix(es):

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, there is an integer overflow in ImageChannel::resize that leads to heap OOB write via OpenEXRUtil public API. This issue has been patched in versions 3.2.9, 3.3.11, and 3.4.11.(CVE-2026-41142)

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.(CVE-2026-42216)

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, readVariableLengthInteger() decodes a variable-length integer from untrusted EXR input without bounding the shift count. After enough continuation bytes, the code executes a left shift by 70 on a 64-bit value, which is undefined behavior. This issue has been patched in versions 3.2.9, 3.3.11, and 3.4.11.(CVE-2026-42217)
Timeline
Published22 May 2026
Updated22 May 2026
First seen22 May 2026
Sources
Track software like this
Free during beta