Bug 2523747 (CVE-2026-68515) - CVE-2026-68515 OpenEXR: OpenEXR: Heap out-of-bounds write in exrmultiview via crafted EXR files
Summary: CVE-2026-68515 OpenEXR: OpenEXR: Heap out-of-bounds write in exrmultiview via...
Keywords:
Status: NEW
Alias: CVE-2026-68515
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: 2524994 2524993
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-25 19:51 UTC by OSIDB Bzimport
Modified: 2026-08-27 15:25 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-25 19:51:46 UTC
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.


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