CVE-2026-62986 json
OpenEXR: PyOpenEXR deep prefixed RGB stale lane disclosure
published 2026-08-25 2 mo ago modified 2026-09-09 1 mo ago also EUVD-2026-65705
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- openexr openexr 3.3.13, 3.4.14
- openexr Debian 14 3.4.14-0.1
debian advisories DEBIAN-CVE-2026-62986
- python-OpenEXR openSUSE Tumbleweed 3.4.16-1.1
- openexr openSUSE Tumbleweed 3.4.14-1.1
opensuse advisories openSUSE-SU-2026:12184-1openSUSE-SU-2026:11612-1
- openexr Alpine 3.24 3.4.15-r0
alpine advisories ALPINE-CVE-2026-62986
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N |
Affected products
- AcademySoftwareFoundation openexr
Classification
References
- github.com /AcademySoftwareFoundation/openexr/commit/36ff0968de08d7ae80792f9f53402f93433207bb
- github.com /AcademySoftwareFoundation/openexr/commit/5105809507ba572d8cad12ec9f5a5c9d378354b9
- github.com /AcademySoftwareFoundation/openexr/commit/5a534e2228c853034e5cb9d2599ebf82f48f51b0
- github.com /AcademySoftwareFoundation/openexr/security/advisories/GHSA-pf59-r2mc-x746
Sources
- CVE List CVE-2026-62986
- NVD CVE-2026-62986
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.