Crash and heap overflow via unchecked allocation
Published Nov 10, 2025 · Updated Nov 10, 2025
Memory corruption in OpenEXR 3.2.0 through 3.2.4, 3.3.0 through 3.3.5, and 3.4.0 through 3.4.2 allows attackers to crash processes. InputFile.channel() and InputFile.channels() multiply attacker-controlled dataWindow dimensions without bounds checks, pass the result to a Python byte allocation without checking for failure, and then write pixels into the returned buffer. Opening a crafted EXR file or passing crafted Python objects to the deprecated wrapper causes a NULL dereference on 64-bit systems or a heap overflow on 32-bit systems.
Summary
What happened
Memory corruption in OpenEXR 3.2.0 through 3.2.4, 3.3.0 through 3.3.5, and 3.4.0 through 3.4.2 allows attackers to crash processes. InputFile.channel() and InputFile.channels() multiply attacker-controlled dataWindow dimensions without bounds checks, pass the result to a Python byte allocation without checking for failure, and then write pixels into the returned buffer. Opening a crafted EXR file or passing crafted Python objects to the deprecated wrapper causes a NULL dereference on 64-bit systems or a heap overflow on 32-bit systems.
The record
- CVE
- CVE-2025-64182
- Published
- Nov 10, 2025
- Updated
- Nov 10, 2025
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-120, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 2025CVE publishedPublication date reported by the CVE source.
- Nov 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.2.0, < 3.2.5
- Affected versionversion=>= 3.3.0, < 3.3.6
- Affected versionversion=>= 3.4.0, < 3.4.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- write_big_header_then_crash.py proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo