cve.bz

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

8.4 highEPSS 0.4%

High (8.4) in openexr openexr. EPSS 0.4% 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. In versions 3.4.0 through 3.4.9, 3.3.0 through 3.3.9, and 3.2.0 through 3.2.7, `internal_dwa_compressor.h:1040` performs `chan->width * chan->bytes_per_element` in `int32` arithmetic without a `(size_t)` cast. This is the same overflow pattern fixed in other decoders by CVE-2026-34589/34588/34544, but this line was missed. Versions 3.4.10, 3.3.10, and 3.2.8 contain a fix that addresses `internal_dwa_compressor.h:1040`.

Severity

CVSS 4.0

8.4 high
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

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.4% (unchanged from 0.4% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th 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: total, assessed 2026-04-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.
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-40250 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40250?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40250?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-40250 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-40250

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

HTML:

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

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openexr:openexrfrom 3.2.0 before 3.2.8
openexr:openexrfrom 3.3.0 before 3.3.10
openexr:openexrfrom 3.4.0 before 3.4.10

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12openexrno fix listedDEBIAN-CVE-2026-40250
Debian13openexr3.2.12-1~deb13u1DEBIAN-CVE-2026-40250
Debian14openexr3.4.14-0.1DEBIAN-CVE-2026-40250
Ubuntu26.10openexrno fix listedUBUNTU-CVE-2026-40250
openSUSETumbleweedopenexr3.4.9-4.1openSUSE-SU-2026:10665-1
Alpinev3.22openexr3.3.11-r0ALPINE-CVE-2026-40250
Alpinev3.23openexr3.4.13-r0ALPINE-CVE-2026-40250
Alpinev3.24openexr3.4.10-r0ALPINE-CVE-2026-40250
Alpaquitastreamopenexr3.4.10-r0BELL-CVE-2026-40250

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

To mitigate this issue, users should avoid opening or processing untrusted EXR image files. If processing EXR files is necessary, ensure they originate from trusted sources. This operational control reduces the risk of a local attacker exploiting the integer overflow vulnerability.

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-40250.

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