CVE-2026-68515: OpenEXR: Heap out-of-bounds write in exrmultiview with subsampled channel union
OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13, exrmultiview can write past a heap allocation when it combines two attacker-supplied, individually valid scanline EXR files whose union dataWindow is not aligned to one view's channel subsampling. The utility allocates sampled channel storage using a truncated unionwidth / xSampling, then reads the sampled input through a Slice based on the misaligned union window, producing a heap out-of-bounds write. The trigger is normal public-tool processing, such as exrmultiview left A.exr right B.exr out.exr with crafted but valid inputs, so this is not solely an API or caller-precondition issue. 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 to a fixed release to a version that resolves this vulnerability.
Fixed in 3.2.11 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.3.13 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.4.14
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments that use the exrmultiview utility with affected OpenEXR releases are exposed when it processes untrusted or attacker-supplied scanline EXR inputs. The affected version ranges are releases before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13.
What does an attacker need to provide to trigger the flaw?
An attacker needs two individually valid scanline EXR files whose combined union dataWindow is misaligned with one view's channel subsampling. Triggering occurs through normal exrmultiview processing, for example by combining crafted left and right input files into an output EXR.
Is this limited to applications using the OpenEXR API incorrectly?
No. The issue can be triggered through the public exrmultiview tool using normal processing of crafted but valid input files, rather than requiring an API caller to violate a precondition.
Which versions contain the fix?
The issue is fixed in OpenEXR versions 3.2.11, 3.3.13, and 3.4.14.