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% (9th 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

Also known asEUVD-2026-65736 (ENISA EUVD)Source: ENISA EUVD

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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

(2 across 2 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openexr—
  • every version up to 3.4.15-r0: fixed in 3.4.15-r0
—
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 7× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 127 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 27 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-11-12 21:30 UTCEchelonGraph re-scored
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-11-05 08:44 UTCEchelonGraph re-scored
  12. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-28 19:58 UTCEchelonGraph re-scored
  20. 2026-10-28 19:55 UTCOSV refresh
  21. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-25 14:09 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-20 22:55 UTCEchelonGraph re-scored
  6. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-18 03:19 UTCEchelonGraph re-scored
  10. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-13 10:05 UTCEchelonGraph re-scored
  16. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-12 15:45 UTCEchelonGraph re-scored
  18. 2026-10-11 19:30 UTCEchelonGraph re-scored
  19. 2026-10-11 16:45 UTCEchelonGraph re-scored
  20. 2026-10-11 14:06 UTCEchelonGraph re-scored
  21. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-10 11:42 UTCEchelonGraph re-scored
  24. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-09 04:08 UTCEchelonGraph re-scored
  26. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  27. 2026-10-08 02:52 UTCEchelonGraph re-scored
  28. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  29. 2026-10-06 20:45 UTCEchelonGraph re-scored
  30. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-10-06 07:42 UTCEchelonGraph re-scored
  32. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-10-05 05:00 UTCEchelonGraph re-scored
  34. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-10-03 16:21 UTCEchelonGraph re-scored
  36. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-10-02 21:32 UTCEchelonGraph re-scored
  38. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-10-01 20:58 UTCEchelonGraph re-scored
  40. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-09-30 20:14 UTCEchelonGraph re-scored
  42. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  43. 2026-09-30 06:41 UTCEchelonGraph re-scored
  44. 2026-09-28 23:20 UTCEchelonGraph re-scored
  45. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  46. 2026-09-27 22:22 UTCEchelonGraph re-scored
  47. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-09-26 21:58 UTCEchelonGraph re-scored
  49. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  50. 2026-09-24 16:50 UTCEchelonGraph re-scored
  51. 2026-09-24 04:19 UTCEchelonGraph re-scored
  52. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  53. 2026-09-23 03:51 UTCEchelonGraph re-scored
  54. 2026-09-22 03:27 UTCEchelonGraph re-scored
  55. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  56. 2026-09-21 02:57 UTCEchelonGraph re-scored
  57. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  58. 2026-09-20 02:28 UTCEchelonGraph re-scored
  59. 2026-09-19 01:44 UTCEchelonGraph re-scored
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  61. 2026-09-18 01:19 UTCEchelonGraph re-scored
  62. 2026-09-17 00:30 UTCEchelonGraph re-scored
  63. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  64. 2026-09-16 12:18 UTCEchelonGraph re-scored
  65. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  66. 2026-09-15 11:54 UTCEchelonGraph re-scored
  67. 2026-09-13 22:55 UTCEchelonGraph re-scored
  68. 2026-09-12 22:31 UTCEchelonGraph re-scored
  69. 2026-09-11 22:06 UTCEchelonGraph re-scored
  70. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  71. 2026-09-11 09:54 UTCEchelonGraph re-scored
  72. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  73. 2026-09-10 21:40 UTCEchelonGraph re-scored
  74. 2026-09-09 01:11 UTCEchelonGraph re-scored
  75. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile

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 (9th 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.