Skip to main content
CVE-2025-64182VulnerabilityPublished Updated

CVE-2025-64182: AcademySoftwareFoundation openexr · Classic Buffer Overflow

Affects AcademySoftwareFoundation openexrSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubacademysoftwarefoundation/openexrpkg:github/academysoftwarefoundation/openexrOther threatsAffected
  • >=3.2.0 <=3.2.4
  • >=3.3.0 <=3.3.5
  • >=3.4.0 <=3.4.2
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 immediately upgrade all OpenEXR installations to patched versions 3.2.5, 3.3.6, or 3.4.3, depending on their current version branch. For environments where upgrading is not immediately feasible, implement strict input validation and sandboxing of processes handling EXR files to limit the impact of potential exploitation. Disable or replace usage of the legacy OpenEXR Python adapter (OpenEXR.InputFile wrapper) in favor of supported APIs that do not contain this vulnerability. Establish file integrity verification and source validation for all EXR files received from external sources to prevent malicious file ingestion. Incorporate runtime protections such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to mitigate exploitation attempts. Monitor application logs and system behavior for crashes or anomalies related to EXR file processing. Finally, conduct security awareness training for developers and operators about the risks of processing untrusted image files and the importance of timely patching.

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.2.0 through 3.2.4, 3.3.0 through 3.3.5, and 3.4.0 through 3.4.2, a memory safety bug in the legacy OpenEXR Python adapter (the deprecated OpenEXR.InputFile wrapper) allow crashes and likely code execution when opening attacker-controlled EXR files or when passing crafted Python objects. Integer overflow and unchecked allocation in InputFile.channel() and InputFile.channels() can lead to heap overflow (32 bit) or a NULL deref (64 bit). Versions 3.2.5, 3.3.6, and 3.4.3 contain a patch for the issue.

References

Community reviews

Loading reviews…