OESA-2026-4683: OpenEXR security update
OpenEXR is a high dynamic-range (HDR) image file format originally developed by Industrial Light & Magic for use in computer imaging applications. Security Fix(es):
OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 are vulnerable on ILP32 builds to an out-of-bounds read. The vulnerability is reached when a crafted uncompressed deep-tile EXR causes the sample-count table size calculation in OpenEXRCore decoding.c to wrap before unpacksampletable() iterates over the full attacker-controlled tile dimensions, allowing denial of service. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.(CVE-2026-59983)
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.(CVE-2026-68515)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/OpenEXRto a version that resolves this vulnerability.Fixed in 3.1.11-10.oe2403sp1 - Upgrade
Upgrade
OpenEXRto a version that resolves this vulnerability.Fixed in 3.2.11
Event History
Frequently Asked Questions
Which installations are affected by the out-of-bounds read issue?
The out-of-bounds read affects ILP32 builds of OpenEXR before 3.2.11, versions 3.3.0 through 3.3.12, and versions 3.4.0 through 3.4.13. It is fixed in 3.2.11, 3.3.13, and 3.4.14.
What is required to trigger the denial-of-service condition?
An attacker needs a crafted uncompressed deep-tile EXR file. The vulnerable decoder processes attacker-controlled tile dimensions after a sample-count table size calculation wraps, resulting in an out-of-bounds read and denial of service.
When is exrmultiview exposed to the heap write issue?
The issue occurs when exrmultiview combines two attacker-supplied, individually valid scanline EXR files whose combined dataWindow is not aligned to one view's channel subsampling. Affected versions are before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13.