CVE-2026-68513

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 25, 2026
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 advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
openexr3.1.13-2, 3.4.6+ds-1, 3.4.6+ds-2, 3.4.6+ds-3, 3.4.6+ds-4
  • every version up to 3.4.14-0.1: fixed in 3.4.14-0.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 53× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-13 10:05 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-10-12 15:45 UTCEG score recompute
  5. 2026-10-11 19:30 UTCEG score recompute
  6. 2026-10-11 16:45 UTCEG score recompute
  7. 2026-10-11 14:06 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-10 11:42 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-09 04:08 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-08 02:52 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-06 20:45 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-06 07:42 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-05 05:00 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-03 16:21 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-02 21:32 UTCEG score recompute
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 64 more
  1. 2026-10-01 20:58 UTCEG score recompute
  2. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-09-30 20:14 UTCEG score recompute
  4. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-09-30 06:41 UTCEG score recompute
  6. 2026-09-28 23:20 UTCEG score recompute
  7. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-09-27 22:22 UTCEG score recompute
  9. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-09-26 21:58 UTCEG score recompute
  11. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-09-24 16:50 UTCEG score recompute
  13. 2026-09-24 04:19 UTCEG score recompute
  14. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-09-23 03:51 UTCEG score recompute
  16. 2026-09-22 03:27 UTCEG score recompute
  17. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-09-21 02:57 UTCEG score recompute
  19. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-09-20 02:28 UTCEG score recompute
  21. 2026-09-19 01:44 UTCEG score recompute
  22. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-09-18 01:19 UTCEG score recompute
  24. 2026-09-17 00:30 UTCEG score recompute
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  26. 2026-09-16 12:18 UTCEG score recompute
  27. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  28. 2026-09-15 11:54 UTCEG score recompute
  29. 2026-09-13 22:55 UTCEG score recompute
  30. 2026-09-12 22:31 UTCEG score recompute
  31. 2026-09-11 22:06 UTCEG score recompute
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-09-11 09:54 UTCEG score recompute
  34. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-09-10 21:40 UTCEG score recompute
  36. 2026-09-09 01:11 UTCEG score recompute
  37. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  38. 2026-09-07 16:08 UTCEG score recompute
  39. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-09-06 15:43 UTCEG score recompute
  41. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-09-06 03:31 UTCEG score recompute
  43. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  44. 2026-09-04 14:49 UTCEG score recompute
  45. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  46. 2026-09-03 02:07 UTCEG score recompute
  47. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-09-02 01:24 UTCEG score recompute
  49. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  50. 2026-09-01 13:01 UTCEG score recompute
  51. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  52. 2026-08-31 00:21 UTCEG score recompute
  53. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  54. 2026-08-30 12:09 UTCEG score recompute
  55. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  56. 2026-08-28 23:28 UTCEG score recompute
  57. 2026-08-28 22:51 UTCEG score recompute
  58. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  59. 2026-08-27 21:15 UTCEG score recompute
  60. 2026-08-26 20:49 UTCEG score recompute
  61. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  62. 2026-08-25 20:23 UTCEG score recompute
  63. 2026-08-25 19:25 UTCEG score recomputeFirst assessed: 7.1 HIGH
  64. 2026-08-25 19:24 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-68513?
CVE-2026-68513 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-68513 published?
The CVE record for CVE-2026-68513 was published on August 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-68513 actively exploited?
CVE-2026-68513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68513?
CVE-2026-68513 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68513?
A fix for CVE-2026-68513 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs