Skip to content
Fencer Intel
medium 5.5

CVE-2026-59984 json

OpenEXR: Scratch buffer overflow decoding B44-compressed InputFile on ILP32

published 3mo ago modified 2mo ago also EUVD-2026-65693 , GHSA-92pq-9qv4-g68q

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
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
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. OpenEXR versions 3.1.0 through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 are vulnerable on ILP32 builds to an out-of-bounds write. When a crafted B44-compressed scanline EXR causes the logical scratch size to truncate before allocation and uncompress_b44_impl() writes using the attacker-controlled channel width, allowing denial of service and memory corruption. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.

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-59984

  • openexr SLES for SAP applications 16.0, SLES 16.0 3.2.2-160000.10.1

suse advisories SUSE-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 Alpine 3.24 3.4.15-r0

alpine advisories ALPINE-CVE-2026-59984

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-59984 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-59984 updated cvss 5.5

OpenEXR: OpenEXR: Denial of service and memory corruption via crafted B44-compressed EXR

  • Red Hat All currently supported Red Hat products
    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.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-92pq-9qv4-g68q referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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.