CVE-2026-59983

Description

A flaw was found in OpenEXR. A remote attacker could exploit an out-of-bounds read vulnerability by providing a specially crafted uncompressed deep-tile EXR image file. This crafted file causes an error in the sample-count table size calculation, leading to a wrap-around before processing the full image dimensions. This can result in a denial of service (DoS), making the application unavailable.

Statement

This Moderate impact flaw in OpenEXR affects ILP32 builds, leading to a denial of service when processing a specially crafted deep-tile EXR file. Exploitation requires user interaction to open the malicious file. Red Hat Enterprise Linux 8 is affected, while Red Hat Enterprise Linux 9 and 10 are not vulnerable due to the absence of the affected code.

Mitigation

To mitigate this issue, avoid processing untrusted EXR image files with applications utilizing OpenEXR. Where feasible, run applications that process EXR files within a sandboxed environment to limit potential impact.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/A5.5
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.