Code execution via unchecked EXR copy length
Published Dec 23, 2025 · Updated Dec 23, 2025
Heap-based buffer overflow in OpenEXR 3.4.0 allows remote attackers to execute code after a user opens a crafted EXR file. The EXR parser accepts a user-controlled length without validating it against the destination allocation before copying data into a heap buffer. Exploitation requires user interaction and runs attacker code in the context of the process that parses the file.
Summary
What happened
Heap-based buffer overflow in OpenEXR 3.4.0 allows remote attackers to execute code after a user opens a crafted EXR file. The EXR parser accepts a user-controlled length without validating it against the destination allocation before copying data into a heap buffer. Exploitation requires user interaction and runs attacker code in the context of the process that parses the file.
The record
- CVE
- CVE-2025-12840
- Published
- Dec 23, 2025
- Updated
- Dec 23, 2025
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-122, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2025CVE publishedPublication date reported by the CVE source.
- Dec 23, 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.4.0
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
No public exploit references are available in this record.
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