CVE-2026-59982

OpenEXR: DWAA InputFile AC buffer overflow on ILP32 platforms

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. OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 can return an out-of-bounds pointer from TypedDeepImageChannel::row() when a crafted deep EXR has a nonzero dataWindow origin. This vulnerability occurs because the API combines zero-based row access with an absolute-coordinate-adjusted base pointer, allowing a crash or limited information disclosure. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.

Analysis

AI-generated

Technical impact

The vulnerability is a buffer overflow that occurs when processing deep EXR files with a nonzero dataWindow origin. A crafted file can cause OpenEXR to return an out‑of‑bounds pointer from TypedDeepImageChannel::row(), which can lead to a crash and, in certain circumstances, the disclosure of limited memory contents. The flaw is caused by the combination of zero-based row access with an absolute‑coordinate‑adjusted base pointer, revealing a logic error in the library’s deep‑image handling. The identified weaknesses are Integer Overflow (CWE‑190) and Buffer Overflow (CWE‑787).

Affected Systems

The affected product is AcademySoftwareFoundation’s OpenEXR. Versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 are vulnerable. The fixed release is 3.4.14 (with earlier 3.2.11 and 3.3.13 also containing the fix).

Risk and Exploitability

The CVSS score of 7.1 indicates a high risk of impact, but the EPSS score is not available, so the current exploitation probability cannot be quantified. The vulnerability is not listed as a known exploitable vulnerability in the CISA KEV catalog. The flaw can be triggered by feeding a maliciously crafted EXR file to any application that uses OpenEXR to load deep images, suggesting the likely attack vector is local file processing, though a remote exploitation path could exist if the library is embedded in a network‑accessible service.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to OpenEXR 3.4.14 or later to eliminate the flaw.
  • If an upgrade is not immediately possible, restrict processing of deep EXR files to trusted sources and block untrusted file uploads.
  • Apply a local patch that checks the dataWindow origin before performing row access to prevent out‑of‑bounds pointer calculations during deep image handling.

Generated by OpenCVE AI on August 25, 2026 at 20:09 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 can return an out-of-bounds pointer from TypedDeepImageChannel::row() when a crafted deep EXR has a nonzero dataWindow origin. This vulnerability occurs because the API combines zero-based row access with an absolute-coordinate-adjusted base pointer, allowing a crash or limited information disclosure. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.
Title OpenEXR: DWAA InputFile AC buffer overflow on ILP32 platforms
Weaknesses CWE-190
CWE-787
References
Metrics cvssV3_1

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

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 25, 2026, 7:20 PM
Reserved
Jul 7, 2026, 7:41 PM
Status
Deferred
Published
Aug 25, 2026, 6:17 PM
Modified
Sep 9, 2026, 9:07 PM