CVE-2026-68513
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Exploit Intelligence
EPSS data unavailable for this CVE.
References
Related Vulnerabilities
Other CWE-122 (Heap-based Buffer Overflow) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2015-3113 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2024-26256 | High | 7.8 | 88% | - | Fix |
| CVE-2020-25687 | Medium | 5.9 | 87% | - | Fix |
| CVE-2009-3459 | High | 8.8 | 87% | KEV | Fix |
| CVE-2021-21017 | High | 8.8 | 86% | KEV | - |
| CVE-2020-25683 | Medium | 5.9 | 86% | - | Fix |
Common questions
How do I fix CVE-2026-68513?
No published fix for CVE-2026-68513 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
How severe is CVE-2026-68513?
CVE-2026-68513 has a CVSS v3 base score of 7.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-68513
Markdown
[](https://tridentstack.com/cve/CVE-2026-68513)HTML
<a href="https://tridentstack.com/cve/CVE-2026-68513"><img src="https://tridentstack.com/cve/badge/CVE-2026-68513.svg" alt="CVE-2026-68513"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-25.