CVE-2026-62986

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% 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
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 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 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.3(medium)
EG Risk
19(Track)
EG Risk 19/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. 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 Patch Available🟡 PoC Available

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

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

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

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

Data Freshness Timeline

(refreshed 9× in last 7d / 43× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-18 15:16 UTCEG score recompute
  3. 2026-09-17 13:07 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 10:54 UTCEG score recompute
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 08:46 UTCEG score recompute
  8. 2026-09-14 06:36 UTCEG score recompute
  9. 2026-09-13 04:28 UTCEG score recompute
  10. 2026-09-12 02:19 UTCEG score recompute
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 09:37 UTCEPSS rescore
  13. 2026-09-11 00:11 UTCEG score recompute
  14. 2026-09-09 01:11 UTCEG score recompute
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 22:31 UTCEG score recompute
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 20:22 UTCEG score recompute
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-05 18:14 UTCEG score recompute
  21. 2026-09-05 15:31 UTCEPSS rescore
  22. 2026-09-04 15:54 UTCEG score recompute
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-03 13:46 UTCEG score recompute
  25. 2026-09-02 14:12 UTCEPSS rescore
Show 18 more
  1. 2026-09-02 11:38 UTCEG score recompute
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 09:25 UTCEG score recompute
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-31 07:16 UTCEG score recompute
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 05:04 UTCEG score recompute
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-29 02:54 UTCEG score recompute
  10. 2026-08-28 21:42 UTCEPSS rescore
  11. 2026-08-28 00:44 UTCEG score recompute
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 22:32 UTCEG score recompute
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 20:23 UTCEG score recompute
  16. 2026-08-25 19:20 UTCEG score recompute
  17. 2026-08-25 18:30 UTCEG score recompute
  18. 2026-08-25 18:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62986?
CVE-2026-62986 is a medium vulnerability 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 CVE-2026-62986 disclosed?
CVE-2026-62986 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-62986 actively exploited?
CVE-2026-62986 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 85.6% of all scored CVEs.
What is the CVSS score of CVE-2026-62986?
CVE-2026-62986 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-62986?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62986, 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-62986

Explore →

Is Your Infrastructure Affected by CVE-2026-62986?

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

Start Free Scan →Browse All CVEs