CVE-2026-59184: OpenEXR: OpenEXRUtil FlatImageChannel row nonzero dataWindow heap OOB write

Published Aug 25, 2026
·
Updated

OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. Versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 allow a crafted EXR with a nonzero dataWindow.min to make TypedFlatImageChannel::row() return an invalid heap pointer, causing out-of-bounds or use-after-free writes. This occurs when an application writes rows through FlatHalfChannel::row(). Affected consumers are tools, converters, render pipeline components, or image-processing services that accept untrusted EXR files and use FlatHalfChannel::row() on loaded images. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.

Affected Software

1 affected component
OpenEXR OpenEXR<3.2.11, >=3.3.0<=3.3.12, >=3.4.0<=3.4.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpenEXR to a version that resolves this vulnerability.

    Fixed in 3.2.11
  2. Upgrade

    Upgrade OpenEXR to a version that resolves this vulnerability.

    Fixed in 3.3.13
  3. Upgrade

    Upgrade OpenEXR to a version that resolves this vulnerability.

    Fixed in 3.4.14

Event History

Aug 25, 2026
CVE Published
via MITRE·04:28 PM
Data Sourced
via MITRE·04:28 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are most exposed to this issue?

Tools, converters, render-pipeline components, and image-processing services are affected when they accept untrusted EXR files and write loaded image rows through FlatHalfChannel::row(). The vulnerable condition is a crafted EXR whose dataWindow.min is nonzero.

2

Does exploitation require authentication or user interaction?

The supplied severity vector indicates network reachability, low attack complexity, no privileges required, and user interaction required. The provided details identify crafted EXR input as the exploitation mechanism.

3

Which OpenEXR releases should be used to remediate the issue?

Upgrade to OpenEXR 3.2.11, 3.3.13, or 3.4.14. Affected releases are versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13.

4

What can be done if an upgrade cannot be applied immediately?

Avoid accepting untrusted EXR files in affected processing paths, particularly paths that use FlatHalfChannel::row() on loaded images. Restricting such inputs reduces exposure to crafted files with a nonzero dataWindow.min.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203