CVE-2026-44663

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-06-18 21:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-26 11:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 6.1 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-06-18 21:16 UTC

Last modified

2026-10-26 11:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-190 · Integer overflow

Record status

Analyzed

Affected

• Openexr < 3.4.12

Attack profile CVSS 3.1 · 6.1

Attack vector

Local

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-44663.md and follow it. Check whether this project is affected by CVE-2026-44663. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge