Cyber Resilience

CVE-2025-48072

Memory Safety in Openexr 3.3.2

Public PoCMemory Safety
Published
31 July 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 6.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0049 40th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-48072 is a medium-severity Out-of-bounds Read (CWE-125) vulnerability in Openexr Openexr. Its CVSS base score is 6.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-48072 is a heap-based buffer overflow vulnerability in the OpenEXR reference implementation, version 3.3.2, which provides the specification and codebase for the EXR file format used in the motion picture industry for image storage. The flaw occurs during a read operation due to incorrect pointer arithmetic when decompressing DWAA-packed scan-line EXR files containing a maliciously forged chunk. This issue is classified under CWE-125 (Out-of-bounds Read) and carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H).

Remote attackers can exploit this vulnerability without privileges or user interaction by supplying a specially crafted DWAA-packed scan-line EXR file to an affected OpenEXR parser. Successful exploitation could result in high-impact confidentiality violations, such as information disclosure through memory reads, and high-impact availability disruptions, including denial-of-service via application crashes, potentially leading to remote code execution depending on the context and mitigations in place.

The OpenEXR project has addressed this vulnerability in version 3.3.3, as detailed in the security advisory GHSA-4r7w-q3jg-ff43, the release notes at the v3.3.3 tag, and the fixing commit 2d09449427b13a05f7c31a98ab2c4347c23db361. Security practitioners should update to OpenEXR 3.3.3 or later and validate EXR file inputs where possible to mitigate risks in applications processing motion picture imagery.

EU & UK References

Vulnerability Data

OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. Version 3.3.2 is vulnerable to a heap-based buffer overflow during a read operation due to bad pointer math when…

more

decompressing DWAA-packed scan-line EXR files with a maliciously forged chunk. This is fixed in version 3.3.3.

CWE(s)
CWE-125

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-45696Same product: Openexr Openexr
CVE-2026-42216Same product: Openexr Openexr
CVE-2026-34588Same product: Openexr Openexr
CVE-2026-34380Same product: Openexr Openexr
CVE-2026-44663Same product: Openexr Openexr
CVE-2023-5841Same product: Openexr Openexr
CVE-2026-34589Same product: Openexr Openexr
CVE-2026-34379Same product: Openexr Openexr
CVE-2026-27622Same product: Openexr Openexr
CVE-2026-34544Same product: Openexr Openexr

Affected Assets

openexr
openexr
3.3.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation directly finds out-of-bounds read flaws through static analysis, fuzzing, and dynamic bounds checks.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require bounds checking and memory-safe constructs that stop out-of-bounds reads from being introduced.

SC-39 Process Isolation partial match

Process isolation confines the effects of an out-of-bounds read to the compromised process.

SI-10 Information Input Validation partial match

Input validation rejects malformed indices or lengths that would otherwise cause reads outside buffer bounds.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing out-of-bounds read flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.

A.8.15 Logging partial match
finds

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

References