CVE-2026-34588: OpenEXR has a signed 32-bit Overflow in PIZ Decoder Leads to OOB Read/Write
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From 3.1.0 to before 3.2.7, 3.3.9, and 3.4.9, internal_exr_undo_piz() advances the working wavelet pointer with signed 32-bit arithmetic. Because nx, ny, and wcount are int, a crafted EXR file can make this product overflow and wrap. The next channel then decodes from an incorrect address. The wavelet decode path operates in place, so this yields both out-of-bounds reads and out-of-bounds writes. 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
A specially crafted EXR image can trigger unsafe memory access when opened or processed by vulnerable OpenEXR versions. This may expose data, corrupt processing results, or crash the affected application. Risk is greatest in services and creative pipelines that accept EXR files from untrusted sources.
Executive priority
Treat remediation as high priority, especially for public upload services and automated media pipelines. Patch exposed systems promptly and restrict untrusted EXR processing where immediate upgrades are impractical. Less-exposed desktop systems should follow through the normal urgent patch cycle.
Technical view
Signed 32-bit arithmetic in internal_exr_undo_piz() can overflow while advancing a PIZ wavelet pointer. The wrapped value causes the next channel to decode from an incorrect address. Because decoding occurs in place, the flaw permits out-of-bounds reads and writes. CVSS 3.1 rates it 8.8 with user interaction required.
Likely exposure
Exposure exists where OpenEXR 3.1.0 through 3.1.13, vulnerable 3.2.x, 3.3.x, or 3.4.x releases process attacker-controlled EXR images. Likely locations include image-upload services, render pipelines, media-processing systems, and applications embedding the library. The bundle does not identify every downstream product.
Exploitation context
Exploitation requires a crafted EXR file to be opened or processed. The supplied bundle marks KEV false, and no cited source reports active exploitation. Out-of-bounds reads and writes create serious confidentiality, integrity, and availability risk, but the provided evidence does not establish reliable code execution.
Researcher notes
The defect combines CWE-190 integer overflow with CWE-125 and CWE-787 memory access violations. nx, ny, and wcount are signed integers whose product can wrap during PIZ decoding. Assessment should focus on reachable PIZ decode paths, bundled library copies, static linking, and downstream packages carrying backports.
Mitigation direction
Upgrade 3.2.x deployments to OpenEXR 3.2.7 or later.
Upgrade 3.3.x deployments to OpenEXR 3.3.9 or later.
Upgrade 3.4.x deployments to OpenEXR 3.4.9 or later.
Move affected 3.1.x deployments to a supported fixed release.
Restrict processing of untrusted EXR files until upgrades are complete.
Validation and detection
Inventory direct and transitive OpenEXR dependencies across applications, containers, workstations, and processing services.
Confirm deployed versions fall outside all listed vulnerable ranges.
Identify workflows that accept EXR files from external or untrusted sources.
Retest EXR decoding and dependent image workflows after upgrading.
Review Red Hat advisories for distribution-specific package status and updates.
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-125: 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.
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
21Source 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.