CVE-2026-59981: OpenEXR: Heap OOB read in SampleCountChannel row when using nonzero dataWindow
OpenEXR is the reference implementation and specification for the EXR image file format, widely used in the motion picture industry. In versions through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13, the OpenEXRUtil library returns an out-of-bounds pointer from the SampleCountChannel::row() API when a deep image has a non-zero dataWindow origin. The row() accessor is documented as 0-based and computes its address from an internal base that is offset for absolute pixel coordinates, so the two coordinate models conflict whenever dataWindow.min is non-zero. For a deep image whose data window has a large negative vertical origin, row(0) points far outside the allocated sample-count buffer. An application that opens an attacker-controlled deep EXR file and accesses sample counts through row() performs an out-of-bounds read, which can crash the process or, under a controlled heap layout, return adjacent heap memory as sample-count values. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenEXRto a version that resolves this vulnerability.Fixed in 3.2.11 - Upgrade
Upgrade
OpenEXRto a version that resolves this vulnerability.Fixed in 3.3.13 - Upgrade
Upgrade
OpenEXRto a version that resolves this vulnerability.Fixed in 3.4.14
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Applications using the OpenEXRUtil library are exposed if they open attacker-controlled deep EXR files and access sample counts through SampleCountChannel::row(). The triggering image must have a non-zero dataWindow origin; a large negative vertical origin can make row(0) point far outside the allocated buffer.
Does exploitation require authentication or user interaction?
The supplied severity vector indicates network attack access, low attack complexity, no privileges required, and user interaction required. The described trigger is an application processing an attacker-controlled deep EXR file.
What versions contain the fix?
The issue is fixed in OpenEXR versions 3.2.11, 3.3.13, and 3.4.14. Affected releases include versions through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13.
What can happen if a vulnerable application processes a crafted file?
The out-of-bounds read can crash the process. With a controlled heap layout, adjacent heap memory may be returned as sample-count values.