Skip to content
Fencer Intel
high 7.1

CVE-2026-59189 json

OpenEXR: Out-of-bounds read in DeepImageChannel::row() for non-zero dataWindow origin

published 3mo ago modified 2mo ago also EUVD-2026-65593 , GHSA-hwmv-39v6-739m

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository AcademySoftwareFoundation/openexr. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In OpenEXRUtil versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.12, the documented TypedDeepImageChannel<T>::row() API can return an out-of-bounds pointer when a deep image has a non-zero dataWindow origin, resulting in a heap out-of-bounds read and crash, with potential information disclosure under a controlled heap layout. The flaw arises because ImfDeepImageChannel uses two conflicting coordinate models: at(x, y) uses absolute coordinates (with _base offset by dataWindow.min), while row(r) is documented as 0-based logical access. For a non-zero dataWindow.min, row(0) therefore points outside the _sampleListPointers allocation instead of at the first logical row. This issue is fixed in versions 3.3.13 and 3.4.13.

Patch / fix

  • openexr openexr 3.2.11, 3.3.13, 3.4.14
  • openexr Debian 13 3.2.12-1~deb13u1
  • openexr Debian 14 3.4.14-0.1

debian advisories DEBIAN-CVE-2026-59189

  • openexr RHEL 10.2 3.1.10-8.el10_2.5
  • openexr-libs RHEL 10.2 3.1.10-8.el10_2.5
  • OpenEXR RHEL 8 2.2.0-12.el8_10.3
  • OpenEXR-libs RHEL 8 2.2.0-12.el8_10.3

red hat advisories RHSA-2026:84796RHSA-2026:82345

  • openexr SLES for SAP 15 SP6, SLES for SAP 15 SP5, SLES for SAP 15 SP4 +8 more 2.2.1-150000.3.55.1
  • openexr SLES for SAP applications 16.0, SLES 16.0 3.2.2-160000.10.1

suse advisories SUSE-SU-2026:4003-1SUSE-SU-2026:23604-1

  • python-OpenEXR openSUSE Tumbleweed 3.4.16-1.1
  • openexr openSUSE Leap 16.0 3.2.2-160000.10.1
  • openexr openSUSE Tumbleweed 3.4.14-1.1

opensuse advisories openSUSE-SU-2026:12184-1openSUSE-SU-2026:21737-1openSUSE-SU-2026:11612-1

  • openexr AlmaLinux 10 3.1.10-8.el10_2.5
  • openexr-libs AlmaLinux 10 3.1.10-8.el10_2.5
  • OpenEXR-libs AlmaLinux 8 2.2.0-12.el8_10.3

almalinux advisories ALSA-2026:84796ALSA-2026:82345

  • openexr Rocky Linux 9 3.1.1-3.el9_8.5
  • openexr Rocky Linux 10 3.1.10-8.el10_2.5
  • OpenEXR Rocky Linux 8 2.2.0-12.el8_10.3

rocky linux advisories RLSA-2026:86983RLSA-2026:84796RLSA-2026:82345

  • openexr Alpine 3.24 3.4.15-r0

alpine advisories ALPINE-CVE-2026-59189

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-59189 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-59189 updated cvss 7.1

OpenEXR: OpenEXR: Information disclosure and denial of service due to out-of-bounds read

  • Red Hat Enterprise Linux AppStream (v. 8) OpenEXR 2.2.0-12.el8_10.3, OpenEXR-libs 2.2.0-12.el8_10.3
    fixed: vendor fix “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.” RHSA-2026:82345
  • Red Hat Enterprise Linux AppStream (v. 9) openexr 3.1.1-3.el9_8.5, openexr 3.1.1-6.el9_9.2, openexr-libs 3.1.1-3.el9_8.5, openexr-libs 3.1.1-6.el9_9.2
    fixed: vendor fix “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.” RHSA-2026:86983
  • Red Hat Enterprise Linux AppStream (v. 10) openexr 3.1.10-8.el10_2.5, openexr 3.1.10-12.el10_3.2, openexr-libs 3.1.10-8.el10_2.5, openexr-libs 3.1.10-12.el10_3.2
    fixed: vendor fix “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.” RHSA-2026:84796
  • Red Hat Enterprise Linux CodeReady Linux Builder (v. 9) openexr-devel 3.1.1-3.el9_8.5, openexr-devel 3.1.1-6.el9_9.2, openexr-debuginfo 3.1.1-3.el9_8.5, openexr-debuginfo 3.1.1-6.el9_9.2, openexr-debugsource 3.1.1-3.el9_8.5, openexr-debugsource 3.1.1-6.el9_9.2, +2 more
    fixed: vendor fix “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.” RHSA-2026:86983
  • Red Hat Enterprise Linux CodeReady Linux Builder (v. 10) openexr-devel 3.1.10-8.el10_2.5, openexr-devel 3.1.10-12.el10_3.2, openexr-debuginfo 3.1.10-8.el10_2.5, openexr-debuginfo 3.1.10-12.el10_3.2, openexr-debugsource 3.1.10-8.el10_2.5, openexr-debugsource 3.1.10-12.el10_3.2, +2 more
    fixed: vendor fix “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.” RHSA-2026:84796
  • Red Hat Enterprise Linux CRB (v. 8) OpenEXR-devel 2.2.0-12.el8_10.3, OpenEXR-debuginfo 2.2.0-12.el8_10.3, OpenEXR-debugsource 2.2.0-12.el8_10.3, OpenEXR-libs-debuginfo 2.2.0-12.el8_10.3
    fixed: vendor fix “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.” RHSA-2026:82345
  • Red Hat Enterprise Linux 6 OpenEXR, OpenEXR-libs Red Hat Enterprise Linux 7 OpenEXR, OpenEXR-libs
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-hwmv-39v6-739m referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H

Inferred packages

No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.

ecosystem package repository affected
pypi openexr academysoftwarefoundation/openexr no versions given

Affected products

  • AcademySoftwareFoundation openexr

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of AcademySoftwareFoundation/openexr published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.