CVE-2026-59187
Description
A flaw was found in OpenEXR. The exrmetrics tool is vulnerable to a heap out-of-bounds write when processing a specially crafted deep scanline EXR image. This occurs during pixel conversion operations, where the tool attempts to write floating-point data into buffers allocated for half-float data. A remote attacker could exploit this vulnerability by providing a malicious EXR file, leading to a denial of service.
Statement
This Important vulnerability in OpenEXR, a heap out-of-bounds write in exrmetrics, does not affect Red Hat products. The vulnerable code is not present in the versions of OpenEXR shipped with Red Hat Enterprise Linux and other Red Hat offerings.
Mitigation
To mitigate this issue, avoid processing untrusted EXR files with the `exrmetrics` utility, especially when using the `--pixelmode float` or `--bench` pixel conversion options. Exercise caution when handling EXR files from unknown or untrusted sources.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.1 | N/A | 7.1 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
