LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41142: OpenEXR is Vulnerable to Integer overflow in ImageChannel::resize leads to heap OOB write via OpenEXRUtil public API

OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From versions 3.0.0 to before 3.2.9, 3.3.0 to before 3.3.11, and 3.4.0 to before 3.4.11, there is an integer overflow in ImageChannel::resize that leads to heap OOB write via OpenEXRUtil public API. This issue has been patched in versions 3.2.9, 3.3.11, and 3.4.11.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OpenEXR contains a memory-corruption flaw that can be triggered when affected software uses the OpenEXRUtil API to resize image-channel data. Processing attacker-controlled input could compromise confidentiality, integrity, and availability, but user interaction is required. Patched releases are available.

Executive priority

Prioritize systems that ingest externally supplied images or support production rendering and media workflows. Patch promptly because memory corruption may affect sensitive data and service availability. Internet delivery alone is insufficient; required user interaction and API reachability should guide sequencing. There is no supplied evidence of active exploitation.

Technical view

OpenEXR 3.0.0 through 3.2.8, 3.3.0 through 3.3.10, and 3.4.0 through 3.4.10 contain an integer overflow in ImageChannel::resize. The overflow can cause a heap out-of-bounds write through the public OpenEXRUtil API. CVSS 3.1 rates it 8.8 with network reachability, low complexity, no privileges, and required user interaction.

Likely exposure

Exposure is most likely where applications, rendering pipelines, media services, or embedded dependencies use an affected OpenEXR version and invoke the vulnerable OpenEXRUtil functionality on untrusted content. Installing OpenEXR does not alone prove reachability; dependency versions and actual API usage require validation.

Exploitation context

The supplied record does not identify confirmed active exploitation, and the CVE is not marked as CISA KEV. The CVSS assessment indicates a network-deliverable attack requiring user interaction. The sources establish possible high confidentiality, integrity, and availability impact, but do not establish reliable code execution or observed attacks.

Researcher notes

Reachability analysis should focus on calls into OpenEXRUtil ImageChannel::resize and whether attacker-influenced dimensions reach that path. Review embedded or statically linked copies that package inventories may miss. The source bundle confirms heap corruption but does not document exploitation reliability, attack prevalence, or a demonstrated outcome beyond the CVSS impact assessment.

Mitigation direction

  • Upgrade 3.0.x–3.2.x deployments to OpenEXR 3.2.9 or later.
  • Upgrade 3.3.x deployments to OpenEXR 3.3.11 or later.
  • Upgrade 3.4.x deployments to OpenEXR 3.4.11 or later.
  • Apply applicable Red Hat security updates for distribution-managed packages.
  • Until upgraded, avoid processing untrusted EXR content through affected components.

Validation and detection

  • Inventory direct, transitive, bundled, and statically linked OpenEXR versions.
  • Identify applications invoking ImageChannel::resize through the OpenEXRUtil API.
  • Trace externally supplied EXR content to potentially affected processing paths.
  • Confirm deployed packages meet the patched version for their maintained branch.
  • Retest representative EXR workflows after upgrading for operational regressions.
Prepared
Confidence
high
Sources
5

Public sources used

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-41142 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
13Source 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9GitHub_M
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-41142Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPOpenEXR: OpenEXR: Arbitrary code execution via integer overflow in image resizing
other:Red Hat severity ratingcvssV3_1
  • 2026-05-07T05:01:36.385Z: Reported to Red Hat.
  • 2026-05-07T03:58:09.483Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AcademySoftwareFoundationopenexr>= 3.0.0, < 3.2.9, >= 3.3.0, < 3.3.11, >= 3.4.0, < 3.4.11Listed
Weakness

CWE details

CWE-190

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.

Open CWE intelligenceSame-CWE CVEs