cve.bz

CVE-2026-44663 openexr openexr: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.1 highExploit referenceEPSS 0.2%Fix available

High (7.1) in openexr openexr. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-44663 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-44663?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-44663?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-44663 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-44663

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-44663](https://cve.bz/cve/badge/CVE-2026-44663.svg)](https://cve.bz/cve/CVE-2026-44663)

HTML:

<a href="https://cve.bz/cve/CVE-2026-44663"><img src="https://cve.bz/cve/badge/CVE-2026-44663.svg" alt="CVE-2026-44663"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openexr:openexrfrom 3.4.0 before 3.4.12

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14openexr3.4.14-0.1DEBIAN-CVE-2026-44663
Ubuntu25.10, 26.10, Pro:16.04:LTS and 5 moreopenexrno fix listedUBUNTU-CVE-2026-44663
openSUSETumbleweedopenexr3.4.12-1.1openSUSE-SU-2026:10985-1
Alpinev3.23, v3.24openexr3.4.13-r0ALPINE-CVE-2026-44663
Alpaquitastreamopenexr3.4.13-r0BELL-CVE-2026-44663

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This Moderate impact flaw in OpenEXR, present in Red Hat products, arises from an integer overflow when decoding maliciously crafted HTJ2K-compressed EXR files. Successful exploitation requires user interaction to open a specially crafted file, leading to a heap-buffer overflow that can result in denial of service and potential data integrity corruption.

Red Hat's mitigation

To mitigate this issue, avoid processing untrusted HTJ2K-compressed EXR files. Restricting the handling of such files to trusted sources can prevent exploitation of this vulnerability in applications that utilize the OpenEXR library.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10openexrFix deferred
Red Hat Enterprise Linux 6OpenEXROut of support scope
Red Hat Enterprise Linux 7OpenEXROut of support scope
Red Hat Enterprise Linux 8OpenEXRFix deferred
Red Hat Enterprise Linux 9openexrFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-44663.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON