CVE-2026-59982
Received Received - Intake

Heap Buffer Overflow in OpenEXR Image Processing Library

Publication date: 2026-08-25

Last updated on: 2026-08-25

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-25
Last Modified
2026-08-25
Generated
2026-08-25
AI Q&A
2026-08-25
EPSS Evaluated
N/A
NVD
CVE-2026-59982
EUVD
EUVD-2026-65690

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
openexr openexr to 3.2.11 (exc)
openexr openexr From 3.3.0 (inc) to 3.3.12 (inc)
openexr openexr From 3.4.0 (inc) to 3.4.13 (inc)
academysoftwarefoundation openexr to 3.4.13 (inc)
academysoftwarefoundation openexr 3.4.13

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-190 The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

OpenEXR before versions 3.2.11, 3.3.13, and 3.4.14 has a flaw in TypedDeepImageChannel::row() where a crafted deep EXR file with a nonzero dataWindow origin can cause the function to return an out-of-bounds pointer. This happens because the API incorrectly combines zero-based row access with an absolute-coordinate-adjusted base pointer, potentially leading to crashes or limited information disclosure.

Detection Guidance

Detecting this vulnerability requires checking the installed version of OpenEXR. Use commands like 'exrheader --version' or 'dpkg -l | grep openexr' on Linux to verify if your version is below 3.2.11, 3.3.13, or 3.4.14. If the version is outdated, the system is vulnerable.

Impact Analysis

This vulnerability could allow an attacker to crash the application using OpenEXR or potentially access limited sensitive data. The impact depends on how OpenEXR is used in your environment, but it primarily affects systems processing untrusted EXR files.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR or HIPAA as it relates to memory corruption in OpenEXR image processing. However, if exploited, it could lead to crashes or limited information disclosure, which may indirectly impact data integrity or availability requirements under these regulations.

Mitigation Strategies

Immediately update OpenEXR to the latest patched version (3.2.11, 3.3.13, or 3.4.14). Disable or restrict access to applications using OpenEXR if updating is not possible. Monitor for unusual activity or crashes in image processing software.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-59982. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart