CVE-2026-68513

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github_commit Patch Available

commit d134e3cd81a2 (AcademySoftwareFoundation/openexr)

Patch available: AcademySoftwareFoundation/openexr v3.3.13 (contains commit d134e3cd81a2)

https://github.com/AcademySoftwareFoundation/openexr/commit/d134e3cd81a2e343f2919e86bf949f576b1ab16a
github_commit Patch Available

commit c1f3ec0d91cf (AcademySoftwareFoundation/openexr)

Patch available: AcademySoftwareFoundation/openexr v3.4.14 (contains commit c1f3ec0d91cf)

https://github.com/AcademySoftwareFoundation/openexr/commit/c1f3ec0d91cfa5a8035ecd00920835ac76e01640
github Patch Available🟡 PoC Available

PyOpenEXR prefixed literal RGB key collision heap buffer overflow · Advisory · AcademySoftwareFoundation/openexr · GitHub

https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-rw5h-3q4v-c3vc

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openexr3.1.13-2, 3.4.6+ds-1, 3.4.6+ds-2, 3.4.6+ds-3, 3.4.6+ds-43.4.14-0.1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-21 02:57 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-20 02:28 UTCEG score recompute
  4. 2026-09-19 01:44 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 01:19 UTCEG score recompute
  7. 2026-09-17 00:30 UTCEG score recompute
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 12:18 UTCEG score recompute
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 11:54 UTCEG score recompute
  12. 2026-09-13 22:55 UTCEG score recompute
  13. 2026-09-12 22:31 UTCEG score recompute
  14. 2026-09-11 22:06 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 09:54 UTCEG score recompute
  17. 2026-09-11 09:37 UTCEPSS rescore
  18. 2026-09-10 21:40 UTCEG score recompute
  19. 2026-09-09 01:11 UTCEG score recompute
  20. 2026-09-08 22:01 UTCEPSS rescore
  21. 2026-09-07 16:08 UTCEG score recompute
  22. 2026-09-07 16:01 UTCEPSS rescore
  23. 2026-09-06 15:43 UTCEG score recompute
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-06 03:31 UTCEG score recompute
Show 22 more
  1. 2026-09-05 15:31 UTCEPSS rescore
  2. 2026-09-04 14:49 UTCEG score recompute
  3. 2026-09-04 05:07 UTCEPSS rescore
  4. 2026-09-03 02:07 UTCEG score recompute
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-02 01:24 UTCEG score recompute
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-09-01 13:01 UTCEG score recompute
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-31 00:21 UTCEG score recompute
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 12:09 UTCEG score recompute
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 23:28 UTCEG score recompute
  15. 2026-08-28 22:51 UTCEG score recompute
  16. 2026-08-28 21:42 UTCEPSS rescore
  17. 2026-08-27 21:15 UTCEG score recompute
  18. 2026-08-26 20:49 UTCEG score recompute
  19. 2026-08-26 14:47 UTCEPSS rescore
  20. 2026-08-25 20:23 UTCEG score recompute
  21. 2026-08-25 19:25 UTCEG score recompute
  22. 2026-08-25 19:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-68513?
CVE-2026-68513 is a high vulnerability published on August 25, 2026. 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…
When was CVE-2026-68513 disclosed?
CVE-2026-68513 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68513 actively exploited?
CVE-2026-68513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.3% of all scored CVEs.
What is the CVSS score of CVE-2026-68513?
CVE-2026-68513 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-68513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68513, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68513

Explore →

Is Your Infrastructure Affected by CVE-2026-68513?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs