CVE-2026-61555

OpenEXR: Empty multiView viewFromChannelName file crash

Published Aug 25, 2026 CVSS 3.1 · 5.5 Medium 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. OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 are vulnerable to crashing. This occurs when Imf::GetChannelsInMultiPartFile() processes a crafted EXR with an empty multiView header attribute and Imf::viewFromChannelName() indexes the empty vector for a dotless channel name. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.

Analysis

AI-generated

Technical impact

The flaw occurs when the OpenEXR library processes an EXR file that contains an empty multiView header. Imf::GetChannelsInMultiPartFile() reads the file, and then Imf::viewFromChannelName() attempts to index the empty vector for a dotless channel name, causing an out‑of‑bounds read (CWE‑125). This leads to a crash of the process that handles the image, manifesting as a denial of service. The issue does not provide code execution but disrupts applications that load or render the vulnerable image.

Affected Systems

Academy Software Foundation OpenEXR libraries prior to version 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 are affected. These versions are commonly deployed in the motion‑picture and visual‑effects industry for composing and rendering high‑dynamic‑range imagery. The vulnerability is limited to the native C++ implementation of the OpenEXR reference library.

Risk and Exploitability

The CVSS score of 5.5 indicates moderate severity. No EPSS data is available and the vulnerability is not listed in the CISA KEV catalog, so the likelihood of widespread exploitation is uncertain. An attacker would need to supply a crafted EXR file that includes an empty multiView header; the crash is triggered when Imf::viewFromChannelName() accesses the vector. Thus the attack vector is likely file‑based, through local or remote file upload or ingestion by an application that trusts the image source. The deterministic crash can be used to interrupt services, but it does not enable direct code execution.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade OpenEXR to version 3.2.11 or later, 3.3.13 or later, or 3.4.14 or later.
  • Configure any application that consumes EXR files to validate the file contents before processing, rejecting files that contain an empty multiView header or ensuring the vector sizes are checked.
  • Monitor application logs and system stability for crashes related to EXR file processing, and investigate any unexpected restarts or crash dumps.

Generated by OpenCVE AI on August 25, 2026 at 21:13 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': 'none', '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. OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 are vulnerable to crashing. This occurs when Imf::GetChannelsInMultiPartFile() processes a crafted EXR with an empty multiView header attribute and Imf::viewFromChannelName() indexes the empty vector for a dotless channel name. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.
Title OpenEXR: Empty multiView viewFromChannelName file crash
Weaknesses CWE-125
References
Metrics cvssV3_1

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

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 26, 2026, 6:51 PM
Reserved
Jul 10, 2026, 4:48 PM
Status
Deferred
Published
Aug 25, 2026, 7:16 PM
Modified
Sep 9, 2026, 9:07 PM
Severity
Moderate
Public date
Aug 25, 2026, 6:19 PM