Heap overwrite via unchecked decompressed chunk size
Published Jul 31, 2025 · Updated Jul 31, 2025
Heap-based buffer overflow in OpenEXR 3.3.0 through 3.3.2 allows context-dependent attackers to corrupt process memory via a crafted EXR file. OpenEXRCore's undo_zip_impl passes actual_out_bytes to internal_zip_reconstruct_bytes without checking it against the header-derived output-buffer size. The flaw is reached when a user or application opens a ZIPS-packed deep scan-line file; exploitation can crash the process or execute code.
Summary
What happened
Heap-based buffer overflow in OpenEXR 3.3.0 through 3.3.2 allows context-dependent attackers to corrupt process memory via a crafted EXR file. OpenEXRCore's undo_zip_impl passes actual_out_bytes to internal_zip_reconstruct_bytes without checking it against the header-derived output-buffer size. The flaw is reached when a user or application opens a ZIPS-packed deep scan-line file; exploitation can crash the process or execute code.
The record
- CVE
- CVE-2025-48071
- Published
- Jul 31, 2025
- Updated
- Jul 31, 2025
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 31, 2025CVE publishedPublication date reported by the CVE source.
- Jul 31, 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.3.0, < 3.3.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.
Public exploit references
- heap_overflow.exr 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