cve.bz

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

5.9 mediumExploit referenceEPSS 0.3%

Medium (5.9) 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. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a signed integer overflow exists in undo_pxr24_impl() in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The expression (uint64_t)(w * 3) computes w * 3 as a signed 32-bit integer before casting to uint64_t. When w is large, this multiplication constitutes undefined behavior under the C standard. On tested builds (clang/gcc without sanitizers), two's-complement wraparound commonly occurs, and for specific values of w the wrapped result is a small positive integer, which may allow the subsequent bounds check to pass incorrectly. If the check is bypassed, the decoding loop proceeds to write pixel data through dout, potentially extending far beyond the allocated output buffer. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H
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; 19th 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: no · Technical impact: partial, assessed 2026-04-07. 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-34380 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34380?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34380?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-34380 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-34380

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

HTML:

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

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openexr:openexrfrom 3.2.0 before 3.2.7
openexr:openexrfrom 3.3.0 before 3.3.9
openexr:openexrfrom 3.4.0 before 3.4.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12openexrno fix listedDEBIAN-CVE-2026-34380
Debian13openexr3.2.12-1~deb13u1DEBIAN-CVE-2026-34380
Debian14openexr3.4.14-0.1DEBIAN-CVE-2026-34380
Ubuntu25.10, 26.10openexrno fix listedUBUNTU-CVE-2026-34380
UbuntuPro:16.04:LTSopenexr2.2.0-10ubuntu2.6+esm4USN-8259-1
UbuntuPro:18.04:LTSopenexr2.2.0-11.1ubuntu1.9+esm1USN-8259-1
UbuntuPro:20.04:LTSopenexr2.3.0-6ubuntu0.5+esm2USN-8259-1
UbuntuPro:22.04:LTSopenexr2.5.7-1ubuntu0.1~esm2USN-8259-1
UbuntuPro:24.04:LTSopenexr3.1.5-5.1ubuntu0.1~esm1UBUNTU-CVE-2026-34380 USN-8259-1
UbuntuPro:26.04:LTSopenexr3.1.13-2ubuntu0.26.04.1~esm1UBUNTU-CVE-2026-34380 USN-8259-1
openSUSELeap 16.0openexr3.2.2-160000.6.1openSUSE-SU-2026:20605-1
openSUSETumbleweedopenexr3.4.9-1.1openSUSE-SU-2026:10505-1
Alpinev3.22openexr3.3.11-r0ALPINE-CVE-2026-34380
Alpinev3.23openexr3.4.13-r0ALPINE-CVE-2026-34380
Alpinev3.24openexr3.4.10-r0ALPINE-CVE-2026-34380
Alpaquitastreamopenexr3.4.9-r0BELL-CVE-2026-34380

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

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