cve.bz

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

5.3 mediumExploit referenceEPSS 0.3%

Medium (5.3) in openexr openexr. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. Versions 3.4.0 through 3.4.9 have a signed integer overflow vulnerability in OpenEXR's HTJ2K (High-Throughput JPEG 2000) decompression path. The `ht_undo_impl()` function in `src/lib/OpenEXRCore/internal_ht.cpp` accumulates a bytes-per-line value (`bpl`) using a 32-bit signed integer with no overflow guard. A crafted EXR file with 16,385 FLOAT channels at the HTJ2K maximum width of 32,767 causes `bpl` to overflow `INT_MAX`, producing undefined behavior confirmed by UBSan. On an allocator-permissive host where the required ~64 GB allocation succeeds, the wrapped negative `bpl` value would subsequently be used as a per-scanline pointer advance, which would produce a heap out-of-bounds write. On a memory-constrained host, the allocation fails before `ht_undo_impl()` is entered. This is the second distinct integer overflow in `ht_undo_impl()`. CVE-2026-34545 addressed a different overflow in the same function — the `int16_t p` pixel-loop counter at line ~302 that overflows when iterating over channels whose `width` exceeds 32,767. The CVE-2026-34545 fix did not touch the `int bpl` accumulator at line 211, which is the subject of this advisory. The `bpl` accumulator was also not addressed by any of the 8 advisories in the 2026-04-05 v3.4.9 release batch. This finding is structurally identical to CVE-2026-34588 (PIZ `wcount*nx` overflow in `internal_piz.c`) and should be remediated with the same pattern. The CVE-2026-34588 fix did not touch `internal_ht.cpp`. Version 3.4.10 contains a remediation that addresses the vulnerability in `internal_ht.cpp`.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-04-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
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-39886 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-39886?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-39886?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-39886 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-39886

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-39886](https://cve.bz/cve/badge/CVE-2026-39886.svg)](https://cve.bz/cve/CVE-2026-39886)

HTML:

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

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openexr:openexrfrom 3.4.0 before 3.4.10

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14openexr3.4.14-0.1DEBIAN-CVE-2026-39886
Ubuntu26.10openexrno fix listedUBUNTU-CVE-2026-39886
openSUSETumbleweedopenexr3.4.9-4.1openSUSE-SU-2026:10665-1
Alpinev3.23openexr3.4.13-r0ALPINE-CVE-2026-39886
Alpinev3.24openexr3.4.10-r0ALPINE-CVE-2026-39886
Alpaquitastreamopenexr3.4.10-r0BELL-CVE-2026-39886

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 mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10openexrFix deferred
Red Hat Enterprise Linux 6OpenEXRFix deferred
Red Hat Enterprise Linux 7OpenEXRFix deferred
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-39886.

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