Description
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a signed integer overflow exists in undo_pxr24_impl() in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The expression (uint64_t)(w * 3) computes w * 3 as a signed 32-bit integer before casting to uint64_t. When w is large, this multiplication constitutes undefined behavior under the C standard. On tested builds (clang/gcc without sanitizers), two's-complement wraparound commonly occurs, and for specific values of w the wrapped result is a small positive integer, which may allow the subsequent bounds check to pass incorrectly. If the check is bypassed, the decoding loop proceeds to write pixel data through dout, potentially extending far beyond the allocated output buffer. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
Published: 2026-04-06
Score: 5.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Memory corruption with potential for arbitrary code execution
Action: Patch
AI Analysis

Impact

OpenEXR contains a signed integer overflow in the undo_pxr24_impl function of the PXR24 decompression routine, which can lead to a bounds‑check bypass. The overflow occurs when a large value for the width parameter is multiplied by three as a signed 32‑bit integer before being cast to an unsigned 64‑bit value; this undefined behavior can wrap to a small positive number. If the bounds check is incorrectly satisfied, the decompression loop writes pixel data beyond the allocated output buffer, allowing an attacker to corrupt memory and potentially achieve arbitrary code execution. The weakness is characterized as a signed integer overflow (CWE‑190) and out‑of‑bounds write (CWE‑787).

Affected Systems

The vulnerability affects OpenEXR releases from version 3.2.0 up through, but not including, 3.2.7, and analogously from 3.3.0‑3.3.8 and 3.4.0‑3.4.8. The only vendor listed is the Academy Software Foundation, maintaining the openexr library.

Risk and Exploitability

The CVSS base score of 5.9 indicates moderate to high risk, while the EPSS score of less than 1% suggests a low likelihood of exploitation in the wild. The vulnerability is not registered in CISA’s KEV catalog, implying no known active exploitation. Based on the description, the likely attack vector is the processing of a crafted EXR file by an application that incorporates the vulnerable OpenEXR library, which could be local or remote depending on the application’s exposure to untrusted input.

Generated by OpenCVE AI on April 7, 2026 at 21:41 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the OpenEXR library to version 3.2.7 or later, or to 3.3.9 or 3.4.9, which contain the fix for the overflow.

Generated by OpenCVE AI on April 7, 2026 at 21:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 07 Apr 2026 20:45:00 +0000

Type Values Removed Values Added
First Time appeared Openexr
Openexr openexr
CPEs cpe:2.3:a:openexr:openexr:*:*:*:*:*:*:*:*
Vendors & Products Openexr
Openexr openexr

Tue, 07 Apr 2026 15:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 07 Apr 2026 07:15:00 +0000


Tue, 07 Apr 2026 00:00:00 +0000

Type Values Removed Values Added
First Time appeared Academysoftwarefoundation
Academysoftwarefoundation openexr
Vendors & Products Academysoftwarefoundation
Academysoftwarefoundation openexr
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 06 Apr 2026 15:30:00 +0000

Type Values Removed Values Added
Description OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a signed integer overflow exists in undo_pxr24_impl() in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The expression (uint64_t)(w * 3) computes w * 3 as a signed 32-bit integer before casting to uint64_t. When w is large, this multiplication constitutes undefined behavior under the C standard. On tested builds (clang/gcc without sanitizers), two's-complement wraparound commonly occurs, and for specific values of w the wrapped result is a small positive integer, which may allow the subsequent bounds check to pass incorrectly. If the check is bypassed, the decoding loop proceeds to write pixel data through dout, potentially extending far beyond the allocated output buffer. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
Title OpenEXR has a signed integer overflow (undefined behavior) in undo_pxr24_impl may allow bounds-check bypass in PXR24 decompression
Weaknesses CWE-190
CWE-787
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H'}


Subscriptions

Academysoftwarefoundation Openexr
Openexr Openexr
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-04-07T14:15:07.727Z

Reserved: 2026-03-27T13:43:14.370Z

Link: CVE-2026-34380

cve-icon Vulnrichment

Updated: 2026-04-07T14:15:03.874Z

cve-icon NVD

Status : Analyzed

Published: 2026-04-06T16:16:35.400

Modified: 2026-04-07T19:03:08.897

Link: CVE-2026-34380

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-04-06T15:22:40Z

Links: CVE-2026-34380 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-04-08T19:50:45Z

Weaknesses