CVE-2026-34589: OpenEXR: DWA Lossy Decoder Heap Out-of-Bounds Write
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, the DWA lossy decoder constructs temporary per-component block pointers using signed 32-bit arithmetic. For a large enough width, the calculation overflows and later decoder stores operate on a wrapped pointer outside the allocated rowBlock backing store. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
Security readout for executives and security teams
Plain-English summary
OpenEXR versions in the listed 3.2, 3.3, and 3.4 ranges can corrupt memory while decoding specially formed DWA-compressed EXR images. Businesses using OpenEXR in rendering, media ingest, thumbnailing, or image processing should treat this as high priority because confidentiality, integrity, and availability impacts are rated high.
Executive priority
Prioritize remediation for systems processing external EXR files, especially production media pipelines and automated ingest services. The issue is high severity, but available sources do not show known active exploitation.
Technical view
The DWA lossy decoder uses signed 32-bit arithmetic for temporary per-component block pointers. Large image widths can overflow that calculation, causing later stores to write outside the allocated rowBlock buffer. Sources map this to CWE-190 and CWE-787, with CVSS 3.1 score 8.8.
Likely exposure
Exposure is most likely where applications, services, or desktop tools process untrusted or partner-supplied EXR files using OpenEXR 3.2.0-3.2.6, 3.3.0-3.3.8, or 3.4.0-3.4.8.
Exploitation context
The CVSS vector indicates network reachability with low attack complexity, no privileges, and required user interaction. The bundle marks KEV as false, and no provided source states active exploitation.
Researcher notes
Focus review on DWA lossy decode paths and large-width EXR handling. Evidence supports an integer overflow leading to heap out-of-bounds write, but the provided bundle does not include exploit details or downstream product impact beyond OpenEXR.
Mitigation direction
Upgrade OpenEXR to 3.2.7, 3.3.9, 3.4.9, or later supported fixed releases.
Identify statically linked or bundled OpenEXR copies inside media and rendering applications.
Rebuild and redeploy applications that embed affected OpenEXR libraries.
Check distro and vendor advisories for backported fixes and package-specific status.
Validation and detection
Inventory OpenEXR versions across packages, containers, build artifacts, and SBOMs.
Confirm no deployed component uses 3.2.0-3.2.6, 3.3.0-3.3.8, or 3.4.0-3.4.8.
Map workflows that accept EXR files from users, partners, queues, or network shares.
After remediation, verify runtime libraries resolve to a fixed OpenEXR version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.