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 products
openexr: openexr
References4
- github.com/AcademySoftwareFoundation/openexr/security/advisorie… ExploitVendor Advisory
- github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.2.7 ProductRelease Notes
- github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.3.9 ProductRelease Notes
- github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.4.9 ProductRelease Notes
Metrics
- CVSS 3.1
-
5.9
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H - EPSS — exploit probability
- 0% percentile: 19 · as of 12 November 2026
- CWE
- CWE-190CWE-787
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.