CVE-2026-68515

OpenEXR: Heap out-of-bounds write in exrmultiview with subsampled channel union

Published Aug 25, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A vulnerable version of the exrmultiview utility can write beyond the bounds of a heap allocation when it merges two separately valid EXR files whose union dataWindow is misaligned to a view’s channel subsampling. The flaw is a classic bounds checking error (CWE‑122, CWE‑787) that may corrupt arbitrary memory, potentially leading to data corruption, crashes, or other unintended behavior. The issue is triggered by standard public‑tool commands and is not limited to a specific API or environment.

Affected Systems

The Academy Software Foundation’s OpenEXR library is affected in all releases before 3.2.11, 3.3.13, and 3.4.14. The problematic component is the exrmultiview tool, which is part of the OpenEXR distribution for processing EXR image files in the motion‑picture industry.

Risk and Exploitability

The CVSS score of 7.1 reflects a fairly high severity for a typical desktop or server utility. EPSS data are currently unavailable, and the vulnerability is not listed in CISA’s KEV catalog, indicating no known active exploitation at this time. The likely attack path involves an adversary crafting or corrupting two EXR scanline files that, when processed together by exrmultiview, cause a heap overflow. While the tool is typically run locally, the vulnerability could be exploited by an attacker with file‑write permissions on a system that automatically processes EXR files, or by a malicious user leveraging server‑side script interactions that invoke exrmultiview.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to OpenEXR 3.2.11, 3.3.13, or 3.4.14 where the issue has been fixed
  • If immediate upgrade is not possible, restrict the execution of exrmultiview to trusted users and validate incoming EXR files against a strict schema that ensures dataWindow alignment before processing
  • If the tool must remain in use, implement an additional bounds check in the merging routine or replace exrmultiview processing with an alternative implementation that verifies channel subsampling alignment

Generated by OpenCVE AI on August 25, 2026 at 22:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title OpenEXR: Heap out-of-bounds write in exrmultiview with subsampled channel union
Weaknesses CWE-122
CWE-787
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H'}

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 26, 2026, 2:47 PM
Reserved
Jul 30, 2026, 4:19 PM
Status
Deferred
Published
Aug 25, 2026, 8:17 PM
Modified
Sep 9, 2026, 9:07 PM
Severity
Important
Public date
Aug 25, 2026, 7:34 PM