CVE-2026-62986

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd 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

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

4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenEXR is the reference implementation and specification for the EXR image file format, widely used in the motion picture industry. In versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13, the PyOpenEXR Python bindings return stale heap data when reading a crafted deep scanline EXR that uses layer-prefixed RGB channels. With the default channel coalescing (separate_channels=False), the wrapper groups channels such as left.R, left.G, and left.B into a single RGB sample array, but the lane-offset calculation in PyPart::setDeepSliceData() only recognizes the exact unprefixed names G, B, and A. As a result, prefixed channels like left.G and left.B are decoded into lane 0 while lanes 1 and 2 are left uninitialized and returned to Python. A Python application that reads untrusted deep EXR files through the default OpenEXR.File API and then logs, serializes, previews, or otherwise processes the resulting NumPy sample arrays may expose uninitialized same-process heap contents, in addition to receiving incorrect green and blue channel data. This issue is fixed in versions 3.3.13 and 3.4.14.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
20
EG Risk 20/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)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.4%
EPSS %ILE
32nd
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 (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 every mission impact level.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 every mission impact level.

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

Exploitation none (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 (4)

Auto-updated Aug 25, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit 5a534e2228c8 (AcademySoftwareFoundation/openexr)

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

https://github.com/AcademySoftwareFoundation/openexr/commit/5a534e2228c853034e5cb9d2599ebf82f48f51b0
GitHub commit Patch Available

commit 5105809507ba (AcademySoftwareFoundation/openexr)

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

https://github.com/AcademySoftwareFoundation/openexr/commit/5105809507ba572d8cad12ec9f5a5c9d378354b9
GitHub commit

commit 36ff0968de08 (AcademySoftwareFoundation/openexr)

Fix landed in AcademySoftwareFoundation/openexr commit 36ff0968de08 — awaiting tagged release

https://github.com/AcademySoftwareFoundation/openexr/commit/36ff0968de08d7ae80792f9f53402f93433207bb
GitHub advisoryMentions a patch (unverified)

PyOpenEXR deep prefixed RGB stale lane disclosure · Advisory · AcademySoftwareFoundation/openexr · GitHub

https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-pf59-r2mc-x746

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(3)

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 116 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 16 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-62986?
CVE-2026-62986 is a medium-severity vulnerability; its CVE record was published on August 25, 2026. OpenEXR is the reference implementation and specification for the EXR image file format, widely used in the motion picture industry. In versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13, the PyOpenEXR Python bindings return stale heap data when reading a crafted deep scanline EXR that uses…
When was the CVE record for CVE-2026-62986 published?
The CVE record for CVE-2026-62986 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-62986 actively exploited?
CVE-2026-62986 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62986?
CVE-2026-62986 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62986?
A fix for CVE-2026-62986 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-62986

Explore →

Is Your Infrastructure Affected by CVE-2026-62986?

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