Application crash via unchecked EXR image width
Published Apr 6, 2026 · Updated Apr 6, 2026
Integer overflow in OpenEXR 3.4.0 through 3.4.8 allows remote attackers to crash EXR-processing applications via a crafted file. OpenEXRCore accepts a large negative dataWindow.min.x without a bounds check, computes an enormous width, and overflows w * bpc in generic_unpack(). Exploitation requires an application to parse the supplied file; the bounded consequence is termination of that process, not data disclosure or modification.
Summary
What happened
Integer overflow in OpenEXR 3.4.0 through 3.4.8 allows remote attackers to crash EXR-processing applications via a crafted file. OpenEXRCore accepts a large negative dataWindow.min.x without a bounds check, computes an enormous width, and overflows w * bpc in generic_unpack(). Exploitation requires an application to parse the supplied file; the bounded consequence is termination of that process, not data disclosure or modification.
The record
- CVE
- CVE-2026-34378
- Published
- Apr 6, 2026
- Updated
- Apr 6, 2026
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-20, CWE-190, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 2026CVE publishedPublication date reported by the CVE source.
- Apr 6, 2026Record 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.4.0, < 3.4.9
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
- GHSA-v76p-4qvv-vh4g reproduction procedureproof 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