Skip to main content
VulnerabilityPublished Updated

CVE-2025-64183: AcademySoftwareFoundation openexr · Use After Free

Affects AcademySoftwareFoundation openexrSource CVE Database V5

0

Public exploit available · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% 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:N/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: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 openexr to versions 3.2.5, 3.3.6, or 3.4.3 or later, depending on their current version branch. It is essential to audit all Python-based tools and pipelines that utilize openexr bindings to ensure they do not rely on the legacy adapter (pyOpenEXR_old.cpp) or to confirm that patched versions are in use. Where upgrading is not immediately feasible, organizations should implement strict file validation and sandboxing of EXR file processing to limit the impact of malformed files. Monitoring for abnormal crashes or memory errors in image processing applications can help detect exploitation attempts. Additionally, restricting local access to systems handling EXR files and enforcing strict user permissions can reduce the risk of malicious file injection. Development teams should review custom scripts or integrations that parse EXR attributes to avoid unsafe use of Python C API functions on potentially freed objects. Finally, maintain awareness of updates from the AcademySoftwareFoundation and apply security patches promptly.

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, there is a use-after-free in PyObject_StealAttrString of pyOpenEXR_old.cpp. The legacy adapter defines PyObject_StealAttrString that calls PyObject_GetAttrString to obtain a new reference, immediately decrefs it, and returns the pointer. Callers then pass this dangling pointer to APIs like PyLong_AsLong/PyFloat_AsDouble, resulting in a use-after-free. This is invoked in multiple places (e.g., reading PixelType.v, Box2i, V2f, etc.) Versions 3.2.5, 3.3.6, and 3.4.3 fix the issue.

References

Community reviews

Loading reviews…