CVE-2026-41142 Details
Description
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.
A vulnerability exists in OpenEXR versions 3.0.0 prior to 3.0.6, 3.1.0 through 3.1.13, 3.2.0 prior to 3.2.9, 3.3.0 prior to 3.3.11, and 3.4.0 prior to 3.4.11. The issue arises from an integer overflow in the ImageChannel::resize function, which is part of the public OpenEXRUtil API. This overflow allows for a heap out-of-bounds write, creating a potential vulnerability.
Users should update to OpenEXR versions 3.2.9, 3.3.11, or 3.4.11, where this vulnerability has been patched.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 7, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-190 | Integer Overflow or Wraparound | redhat-SADP |
| CWE-190 | Integer Overflow or Wraparound | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| openexr openexr | >= 3.0.0, < 3.2.9 >= 3.3.0, < 3.3.11 >= 3.4.0, < 3.4.11 |
CPE
Remediation
| |
Change History
9 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 26, 2026 | CVE Translated | [email protected] |
| Jul 15, 2026 | CVE Modified | redhat-SADP |
| Jul 14, 2026 | CVE Modified | redhat-SADP |
| Jul 13, 2026 | CVE Modified | redhat-SADP |
| Jun 30, 2026 | CVE Modified | redhat-SADP |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | [email protected] |
| May 8, 2026 | Initial Analysis | [email protected] |
| May 7, 2026 | New CVE Received | [email protected] |