High [CVE-2026-68515] Heap out-of-bounds write in exrmultiview via crafted EXR files
This high-severity Red Hat Linux advisory covers CVE-2026-68515 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 8.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
- < 3.2.11
- < 3.3.0
- < 3.3.12
- < 3.4.0
- < 3.4.13
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
- 3.2.11
- 3.3.13
- 3.4.14
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- To mitigate this issue, avoid processing untrusted or unverified EXR image files with the `exrmultiview` utility. Users should exercise caution when handling EXR files from unknown or suspicious sources. If possible, restrict the execution environment of `exrmultiview` through sandboxing mechanisms to limit potential impact.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.