Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.1

CVE-2026-44663: OpenEXR 3.4.0‑3.4.11 allows crafted image to corrupt memory

CVE-2026-44663 · published 4 months ago
Summary

Versions 3.4.0 through 3.4.11 of OpenEXR can be tricked with a specially made EXR picture into writing data outside the program’s memory area, which could cause a crash or be abused. The problem is fixed in version 3.4.12. Update OpenEXR to 3.4.12 or later to eliminate the risk.

What to do
  • Update bellsoft openexr to version 3.4.13-r0.
  • Update openexr openexr to version 3.4.12 or later.
Affected software
Ecosystem VendorProductAffected versions
Debian:11 debian openexr All versions
Debian:12 debian openexr All versions
Debian:13 debian openexr All versions
Debian:14 debian openexr All versions
– openexr openexr >= 3.4.0, < 3.4.12
cpe:2.3:a:openexr:openexr:*:*:*:*:*:*:*:*
Alpaquita:stream bellsoft openexr >= 3.4.4-r0, < 3.4.13-r0
Fix: upgrade to 3.4.13-r0
Ubuntu:Pro:16.04:LTS canonical openexr All versions
Original advisory text
OpenEXR: Integer overflow in the HTJ2K decoder leads to heap-buffer-overflow
OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In versions 3.4.0 through 3.4.11, an integer overflow in ht_undo_impl() in src/lib/OpenEXRCore/internal_ht.cpp leads to a heap-buffer overflow when decoding a crafted HTJ2K-compressed EXR file. decode->channels[i].width (int32_t) is multiplied by bytes_per_element in 32-bit signed arithmetic. With large widths (e.g., >= 536870912 for FLOAT data), this overflows, producing a corrupted offset that is later used for pointer arithmetic and can cause a heap out-of-bounds write. The same unchecked multiplication pattern appears in two other HTJ2K paths (bytes-per-line accumulation and pixel-line pointer advancement). As with related CVE-2026-34378 through CVE-2026-34589 fixes in other codecs, validating only after the multiplication is too late because the value may already be overflowed. This issue has been fixed in version 3.4.12.
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
7.1 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-190Integer Overflow
CWE-787Out-of-bounds Write
Timeline
Published18 Jun 2026
Updated29 Oct 2026
First seen18 Jun 2026
Track software like this
Free during beta