CVE-2026-62986Public exploitNetwork attack vectorHinoki check available

Heap-data disclosure via prefixed RGB lane misrouting

Published Aug 25, 2026 · Updated Aug 25, 2026

Information disclosure in PyOpenEXR 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13 allows attackers to read stale heap data via crafted EXR files. In PyPart::setDeepSliceData(), exact comparisons recognize only unprefixed G, B, and A names, so prefixed green and blue samples are written to lane 0 while allocated lanes 1 and 2 remain uninitialized. The default OpenEXR.File API must read an attacker-controlled deep scanline image with coalesced channels, after which processing the returned NumPy array can disclose same-process heap contents and corrupt green and blue pixel data.

CVSS severity4.3
Medium
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in PyOpenEXR 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13 allows attackers to read stale heap data via crafted EXR files. In PyPart::setDeepSliceData(), exact comparisons recognize only unprefixed G, B, and A names, so prefixed green and blue samples are written to lane 0 while allocated lanes 1 and 2 remain uninitialized. The default OpenEXR.File API must read an attacker-controlled deep scanline image with coalesced channels, after which processing the returned NumPy array can disclose same-process heap contents and corrupt green and blue pixel data.

The record

CVE
CVE-2026-62986
Published
Aug 25, 2026
Updated
Aug 25, 2026
Vendor
Academy Software Foundation
Product
OpenEXR
Classifications
CWE-200, CWE-457, CWE-908
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 3.3.0, < 3.3.13
  2. Affected versionversion=>= 3.4.0, < 3.4.14

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Academy Software Foundation · OpenEXRversion=>= 3.3.0, < 3.3.13; version=>= 3.4.0, < 3.4.14

Published CVSS scores

4.3GitHub Security AdvisoryCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
CWE-457Use of Uninitialized Variable
CWE-908Use of Uninitialized Resource

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo