CVE-2026-68513

OpenEXR: Heap buffer overflow in PyOpenEXR from literal/prefixed RGB channel name collision

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. Versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13 contain a heap buffer overflow in PyOpenEXR triggered by a channel-name key collision between literal and prefixed RGB channels. When separate_channels=false, PyOpenEXR maps each physical channel name through channelNameToRGBA() and coalesces the results into a shared RGB array. A crafted flat scanline EXR that contains both a literal channel such as left and prefixed channels such as left.R, left.G, and left.B causes these names to collide, so the wrapper reuses an undersized two-dimensional NumPy array for the coalesced RGB slices and writes out of bounds when OpenEXR.File(path) decodes the pixels. This issue is fixed in versions 3.3.13 and 3.4.14.

Analysis

AI-generated

Technical impact

A heap buffer overflow exists in PyOpenEXR when a channel‑name collision occurs between literal (e.g., left) and prefixed RGB channels (e.g., left.R, left.G, left.B). During decoding, the wrapper reuses an undersized NumPy array for the coalesced RGB slices and writes out of bounds, potentially corrupting memory and allowing an attacker to execute arbitrary code. The CVSS score of 7.1 indicates a high‑severity vulnerability.

Affected Systems

The AcademySoftwareFoundation OpenEXR library is affected. Vulnerable releases include 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13. Versions 3.3.13 and 3.4.14, which contain the fix, are not affected.

Risk and Exploitability

The vulnerability carries a CVSS score of 7.1 and is not listed in CISA’s KEV catalog. EPSS is not available, so the exploitation probability is unknown. Attackers can trigger the overflow by supplying a malicious flat‑scanline EXR file. The flaw is local to the process using PyOpenEXR, but if the library is invoked by a server or service that receives untrusted EXR files, the vulnerability could be exploited remotely.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor‑supplied patch by upgrading to OpenEXR 3.3.13 or 3.4.14.
  • If upgrading is not immediately feasible, restrict untrusted EXR processing to a sandboxed environment or disable PyOpenEXR usage for external input.
  • Implement input validation to detect and reject malformed EXR files with channel‑name collisions before decoding, such as by checking that literal and prefixed channel names are not combined.

Generated by OpenCVE AI on August 26, 2026 at 03:12 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. Versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13 contain a heap buffer overflow in PyOpenEXR triggered by a channel-name key collision between literal and prefixed RGB channels. When separate_channels=false, PyOpenEXR maps each physical channel name through channelNameToRGBA() and coalesces the results into a shared RGB array. A crafted flat scanline EXR that contains both a literal channel such as left and prefixed channels such as left.R, left.G, and left.B causes these names to collide, so the wrapper reuses an undersized two-dimensional NumPy array for the coalesced RGB slices and writes out of bounds when OpenEXR.File(path) decodes the pixels. This issue is fixed in versions 3.3.13 and 3.4.14.
Title OpenEXR: Heap buffer overflow in PyOpenEXR from literal/prefixed RGB channel name collision
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 28, 2026, 10:34 PM
Reserved
Jul 30, 2026, 4:19 PM
Status
Deferred
Published
Aug 25, 2026, 8:17 PM
Modified
Sep 9, 2026, 9:07 PM