CVE-2026-62986

published 25 Aug 2026 · updated 25 Aug 2026

OpenEXR: PyOpenEXR deep prefixed RGB stale lane disclosure

4.3MediumCVSS 4.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

OpenEXR is the reference implementation and specification for the EXR image file format, widely used in the motion picture industry. In versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13, the PyOpenEXR Python bindings return stale heap data when reading a crafted deep scanline EXR that uses layer-prefixed RGB channels. With the default channel coalescing (separate_channels=False), the wrapper groups channels such as left.R, left.G, and left.B into a single RGB sample array, but the lane-offset calculation in PyPart::setDeepSliceData() only recognizes the exact unprefixed names G, B, and A. As a result, prefixed channels like left.G and left.B are decoded into lane 0 while lanes 1 and 2 are left uninitialized and returned to Python. A Python application that reads untrusted deep EXR files through the default OpenEXR.File API and then logs, serializes, previews, or otherwise processes the resulting NumPy sample arrays may expose uninitialized same-process heap contents, in addition to receiving incorrect green and blue channel data. This issue is fixed in versions 3.3.13 and 3.4.14.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
AcademySoftwareFoundation>=3.3.0 <3.3.13, >=3.4.0 <3.4.14

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-62986 severity on Zeptric[![CVE-2026-62986](https://zeptric.io/badge/cve/CVE-2026-62986.svg)](https://zeptric.io/cve/CVE-2026-62986)