CVE-2026-59981

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.3% (24th 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-65746 (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.3%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 file format, widely used in the motion picture industry. In versions through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13, the OpenEXRUtil library returns an out-of-bounds pointer from the SampleCountChannel::row() API when a deep image has a non-zero dataWindow origin. The row() accessor is documented as 0-based and computes its address from an internal base that is offset for absolute pixel coordinates, so the two coordinate models conflict whenever dataWindow.min is non-zero. For a deep image whose data window has a large negative vertical origin, row(0) points far outside the allocated sample-count buffer. An application that opens an attacker-controlled deep EXR file and accesses sample counts through row() performs an out-of-bounds read, which can crash the process or, under a controlled heap layout, return adjacent heap memory as sample-count values. This issue is fixed in versions 3.2.11, 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.3%
EPSS %ILE
24th
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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 (4)

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

commit aef02224ba28 (AcademySoftwareFoundation/openexr)

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

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

commit 55b7958ecb5a (AcademySoftwareFoundation/openexr)

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

https://github.com/AcademySoftwareFoundation/openexr/commit/55b7958ecb5ac32c427ff39c1e063f6f7bbee77c
GitHub commit Patch Available

commit 37f03b6ed90f (AcademySoftwareFoundation/openexr)

Patch available: AcademySoftwareFoundation/openexr v3.2.11 (contains commit 37f03b6ed90f)

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

OpenEXRUtil SampleCountChannel row nonzero dataWindow heap OOB read · Advisory · AcademySoftwareFoundation/openexr · GitHub

https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-m799-ffc3-8pxc

Vendor Advisories for CVE-2026-59981(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenexr-0:3.1.1-3.el9_8.52026-10-21redhat
redhatopenexr-0:3.1.10-8.el10_2.52026-10-19redhat
redhatOpenEXR-0:2.2.0-12.el8_10.32026-10-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 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:12(1)
PackageVulnerable rangeFix by version rangeDependents
openexr3.1.13-1 ... 3.4.6+ds-4 (11 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openexr3.1.13-2 ... 3.4.6+ds-4 (7 versions)
  • every version on: no fix on record
—
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(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59981?
CVE-2026-59981 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 file format, widely used in the motion picture industry. In versions through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13, the OpenEXRUtil library returns an out-of-bounds pointer from the…
When was the CVE record for CVE-2026-59981 published?
The CVE record for CVE-2026-59981 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-59981 actively exploited?
CVE-2026-59981 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59981?
CVE-2026-59981 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-59981?
A fix for CVE-2026-59981 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59981 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59981?

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

Book a Demo →Browse All CVEs