CVE-2026-59183

OpenEXR: Signed Integer Overflow Leading to Out-of-Bounds Memory Access in Deep Tile Decoding

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. In versions 3.1.0 through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13, an int32_t multiplication in OpenEXRCore's unpack_sample_table() can overflow while decoding a crafted deep tiled EXR file, producing an invalid pointer that leads to a read from an unmapped memory address and a crash. Because the overflow occurs in the standard decoding path (exr_decoding_run), any application that decodes deep tiled EXR files is affected. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.

Analysis

AI-generated

Technical impact

A signed integer overflow occurs in OpenEXRCore's unpack_sample_table() when decoding a crafted deep tiled EXR file. The overflow produces an invalid pointer that leads to a read from an unmapped memory address and a crash. The vulnerability is a classic Integer Overflow flaw (CWE‑190) and results in a denial‑of‑service condition rather than code execution or data disclosure.

Affected Systems

The flaw affects AcademySoftwareFoundation OpenEXR library versions 3.1.0 through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13. Any application that uses these versions to decode deep tiled EXR images is affected. The issue is fixed in OpenEXR 3.2.11, 3.3.13, and 3.4.14.

Risk and Exploitability

The CVSS score of 5.5 indicates a moderate severity. The EPSS score of < 1% indicates a very low but non‑zero exploitation probability, and the vulnerability is not listed in the CISA KEV catalog, suggesting limited evidence of exploitation. The likely attack vector is via a crafted deep tiled EXR file; an attacker could supply such a file to any program that decodes deep tiled images, causing it to crash and potentially leading to a denial‑of‑service. The vulnerability is exploitable in a local or remote context depending on whether the application accepts user supplied images.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the OpenEXR library to version 3.2.11 or later (3.3.13, 3.4.14) to apply the vendor‑provided fix.
  • If an upgrade is not immediately possible, restrict or disable deep tile decoding or reject deep tiled EXR files to prevent the overflow from occurring.
  • Perform a security test by feeding a malicious deep tiled EXR file to the application to confirm the vulnerability is mitigated after applying the patch.

Generated by OpenCVE AI on August 26, 2026 at 03: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': '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. In versions 3.1.0 through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13, an int32_t multiplication in OpenEXRCore's unpack_sample_table() can overflow while decoding a crafted deep tiled EXR file, producing an invalid pointer that leads to a read from an unmapped memory address and a crash. Because the overflow occurs in the standard decoding path (exr_decoding_run), any application that decodes deep tiled EXR files is affected. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.
Title OpenEXR: Signed Integer Overflow Leading to Out-of-Bounds Memory Access in Deep Tile Decoding
Weaknesses CWE-190
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 25, 2026, 7:05 PM
Reserved
Jul 2, 2026, 7:53 PM
Status
Deferred
Published
Aug 25, 2026, 1:16 AM
Modified
Oct 12, 2026, 3:10 PM
Severity
Moderate
Public date
Aug 25, 2026, 12:45 AM