CVE-2026-34380: CWE-190: Integer Overflow or Wraparound in AcademySoftwareFoundation openexr
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.
AI Analysis
Technical Summary
OpenEXR versions 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9 contain a signed integer overflow in the undo_pxr24_impl() function located in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The multiplication expression (uint64_t)(w * 3) is computed as a signed 32-bit integer before casting, which can cause two's-complement wraparound for large values of w. This wraparound may cause an incorrect bounds check to pass, allowing the decoding loop to write pixel data beyond the allocated buffer, resulting in a potential out-of-bounds write vulnerability. This vulnerability is tracked as CVE-2026-34380 and is associated with CWE-190 (Integer Overflow) and CWE-787 (Out-of-bounds Write). The issue is fixed in versions 3.2.7, 3.3.9, and 3.4.9.
Potential Impact
The vulnerability can lead to out-of-bounds memory writes during image decoding, which may cause application crashes or potentially enable limited code execution or data corruption. The CVSS score of 5.9 reflects a medium severity with network attack vector, high attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, low integrity impact, and high availability impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
This vulnerability is fixed in openexr versions 3.2.7, 3.3.9, and 3.4.9. Users should upgrade to one of these fixed versions or later to remediate the issue. Patch status is not explicitly confirmed by a vendor advisory in the provided data; therefore, users should verify the availability of official patches or updates from the AcademySoftwareFoundation or the openexr project. Until patched, avoid processing untrusted EXR files with affected versions to reduce risk.
CVE-2026-34380: CWE-190: Integer Overflow or Wraparound in AcademySoftwareFoundation openexr
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenEXR versions 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9 contain a signed integer overflow in the undo_pxr24_impl() function located in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The multiplication expression (uint64_t)(w * 3) is computed as a signed 32-bit integer before casting, which can cause two's-complement wraparound for large values of w. This wraparound may cause an incorrect bounds check to pass, allowing the decoding loop to write pixel data beyond the allocated buffer, resulting in a potential out-of-bounds write vulnerability. This vulnerability is tracked as CVE-2026-34380 and is associated with CWE-190 (Integer Overflow) and CWE-787 (Out-of-bounds Write). The issue is fixed in versions 3.2.7, 3.3.9, and 3.4.9.
Potential Impact
The vulnerability can lead to out-of-bounds memory writes during image decoding, which may cause application crashes or potentially enable limited code execution or data corruption. The CVSS score of 5.9 reflects a medium severity with network attack vector, high attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, low integrity impact, and high availability impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
This vulnerability is fixed in openexr versions 3.2.7, 3.3.9, and 3.4.9. Users should upgrade to one of these fixed versions or later to remediate the issue. Patch status is not explicitly confirmed by a vendor advisory in the provided data; therefore, users should verify the availability of official patches or updates from the AcademySoftwareFoundation or the openexr project. Until patched, avoid processing untrusted EXR files with affected versions to reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-27T13:43:14.370Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d3d1a00a160ebd92c130e2
Added to database: 4/6/2026, 3:30:40 PM
Last enriched: 5/13/2026, 2:24:32 AM
Last updated: 5/21/2026, 11:57:02 PM
Views: 53
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.