High [CVE-2026-68515] Heap out-of-bounds write in exrmultiview via crafted EXR files

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 union_width / 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.

A flaw was found in OpenEXR. A remote attacker could exploit this vulnerability by providing specially crafted EXR image files to the exrmultiview utility.

When processing these files, the utility can write beyond its allocated memory on the heap, leading to a heap out-of-bounds write. This could allow an attacker to achieve arbitrary code execution or cause a denial of service (DoS) on the affected system.

Exploitation requires a local attacker to persuade a user to process specially crafted EXR image files.