Skip to content
Fencer Vulns
high 7.1

CVE-2026-68513 json

OpenEXR: Heap buffer overflow in PyOpenEXR from literal/prefixed RGB channel name collision

published 2026-08-25 2 mo ago modified 2026-09-09 1 mo ago also EUVD-2026-65736

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 9%
public exploits
0
none known

Summary

OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. Versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13 contain a heap buffer overflow in PyOpenEXR triggered by a channel-name key collision between literal and prefixed RGB channels. When separate_channels=false, PyOpenEXR maps each physical channel name through channelNameToRGBA() and coalesces the results into a shared RGB array. A crafted flat scanline EXR that contains both a literal channel such as left and prefixed channels such as left.R, left.G, and left.B causes these names to collide, so the wrapper reuses an undersized two-dimensional NumPy array for the coalesced RGB slices and writes out of bounds when OpenEXR.File(path) decodes the pixels. 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-68513

  • 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-68513

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-68513 updated cvss 7.8

OpenEXR: OpenEXR: Heap buffer overflow in PyOpenEXR allows arbitrary code execution via crafted EXR file.

  • Red Hat Enterprise Linux 6 OpenEXR, OpenEXR-libs Red Hat Enterprise Linux 7 OpenEXR, OpenEXR-libs Red Hat Enterprise Linux 8 OpenEXR, OpenEXR-libs Red Hat Enterprise Linux 9 openexr, openexr-libs Red Hat Enterprise Linux 10 openexr
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-rw5h-3q4v-c3vc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Affected products

  • AcademySoftwareFoundation openexr

Classification

Weakness

References

Sources

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.