CVE-2026-59189

Description

A flaw was found in OpenEXR. An attacker could provide a specially crafted deep image that, when processed, would cause an out-of-bounds read in the TypedDeepImageChannel<T>::row() API if the image has a non-zero dataWindow origin. This vulnerability can lead to a heap out-of-bounds read, resulting in a crash (Denial of Service) and potential information disclosure.

Statement

Important severity is assigned to this flaw because an unauthenticated remote attacker can trigger an application crash or potentially read sensitive heap memory without requiring elevated system privileges. In Red Hat Enterprise Linux environments, OpenEXR is provided as a shared parsing library utilized by graphical and image-processing software, meaning exposure is limited to workloads or users actively handling untrusted graphic assets. Successful exploitation requires user interaction or an automated service ingesting externally sourced image files, and while memory corruption can cause a denial of service, arbitrary code execution has not been demonstrated.

Mitigation

To mitigate this issue, avoid processing untrusted EXR deep image files. Limit the use of applications that process EXR deep images to trusted sources only.

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).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.1N/A7.1
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityLowN/ALow
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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.