CVE-2026-34380

OpenEXR has a signed integer overflow (undefined behavior) in undo_pxr24_impl may allow bounds-check bypass in PXR24 decompression

MEDIUM
5.9
CVSS Score
Published: April 6, 2026 at 03:22 PM UTC
Updated: October 26, 2026 at 09:10 PM UTC
2 products affected across 2 vendorsOpenexrOpenexr

Using openexr by AcademySoftwareFoundation?

Get instant alerts when new vulnerabilities affect openexr - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.9
Exploit prediction
EPSS 0.3%
SSVC
PoC

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.2.0 ≤ v < 3.2.73.3.0 ≤ v < 3.3.93.4.0 ≤ v < 3.4.9
3.2.0 ≤ v < 3.2.73.3.0 ≤ v < 3.3.93.4.0 ≤ v < 3.4.9
Affected range stops below 3.2.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.9, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

x_refsource_MISCProductRelease Notes
Source: cverecord
https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.2.7
x_refsource_MISCProductRelease Notes
Source: cverecord
https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.3.9
x_refsource_MISCProductRelease Notes
Source: cverecord
https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.4.9

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.9MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-190CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card