CVE-2025-64181: AcademySoftwareFoundation openexr · Use of Uninitialized Variable
Affects AcademySoftwareFoundation openexrSource CVE Database V5
Not known to be exploited · CVSS 2.0 Low · fixed in 3.3.6 : update AcademySoftwareFoundation openexr when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.3.6
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubacademysoftwarefoundation/openexrpkg:github/academysoftwarefoundation/openexrOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should upgrade OpenEXR installations to versions 3.3.6 or 3.4.3 or later, where the vulnerability is fixed. For environments where immediate upgrading is not feasible, applying runtime memory sanitizers or fuzz testing tools can help detect anomalous behavior related to uninitialized memory usage. Incorporating static code analysis in development pipelines that use OpenEXR can preemptively identify similar issues. Additionally, isolating image processing tasks in sandboxed or containerized environments can limit the impact of potential crashes. Monitoring application logs for unexpected terminations or errors during EXR file handling can provide early warning signs. Organizations should also review their supply chain to ensure third-party tools or plugins using OpenEXR are updated accordingly. Finally, maintaining robust backup and recovery procedures for media assets will mitigate operational risks from unexpected service disruptions.
Description
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In versions 3.3.0 through 3.3.5 and 3.4.0 through 3.4.2, while fuzzing `openexr_exrcheck_fuzzer`, Valgrind reports a conditional branch depending on uninitialized data inside `generic_unpack`. This indicates a use of uninitialized memory. The issue can result in undefined behavior and/or a potential crash/denial of service. Versions 3.3.6 and 3.4.3 fix the issue.
References
- github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-3h9h-qfvw-98hq (opens in a new tab)
- github.com/user-attachments/files/23024726/archive0.zip (opens in a new tab)
- github.com/user-attachments/files/23024736/archive1.zip (opens in a new tab)
- github.com/user-attachments/files/23024740/archive2.zip (opens in a new tab)
- github.com/user-attachments/files/23024744/archive3.zip (opens in a new tab)
- github.com/user-attachments/files/23024746/archive4.zip (opens in a new tab)