Bug 2523671 (CVE-2026-59189) - CVE-2026-59189 OpenEXR: OpenEXR: Information disclosure and denial of service due to out-of-bounds read
Summary: CVE-2026-59189 OpenEXR: OpenEXR: Information disclosure and denial of service...
Keywords:
Status: NEW
Alias: CVE-2026-59189
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2537143 2537144 2537145
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-25 17:02 UTC by OSIDB Bzimport
Modified: 2026-09-19 11:27 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-25 17:02:16 UTC
OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In OpenEXRUtil versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.12, the documented TypedDeepImageChannel<T>::row() API can return an out-of-bounds pointer when a deep image has a non-zero dataWindow origin, resulting in a heap out-of-bounds read and crash, with potential information disclosure under a controlled heap layout. The flaw arises because ImfDeepImageChannel uses two conflicting coordinate models: at(x, y) uses absolute coordinates (with _base offset by dataWindow.min), while row(r) is documented as 0-based logical access. For a non-zero dataWindow.min, row(0) therefore points outside the _sampleListPointers allocation instead of at the first logical row. This issue is fixed in versions 3.3.13 and 3.4.13.


Note You need to log in before you can comment on or make changes to this bug.