CVE-2026-27622: OpenEXR CompositeDeepScanLine integer-overflow leads to heap OOB write
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In CompositeDeepScanLine::readPixels, per-pixel totals are accumulated in vector<unsigned int> total_sizes for attacker-controlled large counts across many parts, total_sizes[ptr] wraps modulo 2^32. overall_sample_count is then derived from wrapped totals and used in samples[channel].resize(overall_sample_count). Decode pointer setup/consumption proceeds with true sample counts, and write operations in core unpack (generic_unpack_deep_pointers) overrun the undersized composite sample buffer. This vulnerability is fixed in v3.2.6, v3.3.8, and v3.4.6.
Security readout for executives and security teams
Plain-English summary
A malicious EXR image can trigger memory corruption when a person opens or imports it with a vulnerable OpenEXR version. The flaw can affect confidentiality, integrity, and availability of the decoding process. It is high severity, but the supplied sources do not establish active exploitation.
Executive priority
Treat as a high-priority patch for media, rendering, and ingestion systems that handle untrusted EXR files. Accelerate remediation where processing runs with broad permissions or accesses sensitive assets. Systems that never process EXR content have substantially lower practical exposure.
Technical view
CompositeDeepScanLine::readPixels accumulates attacker-controlled sample counts in 32-bit unsigned totals. Those totals can wrap, causing allocation of an undersized composite sample buffer. Subsequent decoding uses the true counts, producing a heap out-of-bounds write in generic_unpack_deep_pointers.
Likely exposure
Exposure exists where OpenEXR versions 2.3.0–3.2.5, 3.3.0–3.3.7, or 3.4.0–3.4.5 process untrusted EXR files. Prioritize user-facing import workflows, shared media pipelines, and systems receiving externally supplied imagery.
Exploitation context
The CVSS 4.0 score is 8.4. Exploitation requires local processing and active user interaction, such as opening or importing a crafted file. The CVE is not listed as KEV, and the supplied sources provide no evidence of exploitation in the wild.
Researcher notes
The vulnerable calculation crosses multiple deep-image parts: wrapped per-pixel totals understate overall_sample_count, while pointer consumption follows actual sample counts. Assessment should distinguish installed packages from statically linked or application-bundled copies. The supplied evidence establishes memory corruption but does not document a public exploit or observed attacks.
Mitigation direction
Upgrade OpenEXR to 3.2.6, 3.3.8, or 3.4.6, as appropriate.
Apply relevant operating-system vendor security updates where OpenEXR is distribution-managed.
Restrict untrusted EXR ingestion until vulnerable deployments are upgraded.
Isolate image-processing workloads and minimize their filesystem and network privileges.
Validation and detection
Inventory installed, bundled, and transitively linked OpenEXR versions.
Confirm no affected version ranges remain in production or processing images.
Verify applications load the upgraded library at runtime, not an older bundled copy.
Run existing EXR decoding regression tests after upgrading.
Review asset-ingestion paths for externally supplied EXR content.
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
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.
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.