CVE-2025-64182 json
OpenEXR has buffer overflow in PyOpenEXR_old's channels() and channel()
published 2025-11-10 11 mo ago modified 2026-07-18 3 mo ago also EUVD-2025-50827 , GHSA-vh63-9mqx-wmjr , JLSEC-2026-138 , PYSEC-2026-2851
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi openexr 3.2.5, 3.3.6, 3.4.3
- julia OpenEXR_jll 3.4.4+0
- openexr openexr 3.2.5, 3.3.6, 3.4.3
- openexr openSUSE Tumbleweed 3.4.3-1.1
opensuse advisories openSUSE-SU-2025:15741-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-64182 updated cvss 6.2
openexr: buffer overflow in PyOpenEXR_old's channels() and channel()
-
Red Hat Enterprise Linux 6 OpenEXR, OpenEXR-libs Red Hat Enterprise Linux 7 OpenEXR, OpenEXR-libs Red Hat Enterprise Linux 8 OpenEXR, OpenEXR-libs Red Hat Enterprise Linux 9 openexr, openexr-libs Red Hat Enterprise Linux 10 openexrnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 11 mo ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-vh63-9mqx-wmjr referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.5 | 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 |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 5.5 | 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | openexr | >=3.2.0, <3.2.5 >=3.3.0, <3.3.6 >=3.4.0, <3.4.3 |
3.2.5 3.3.6 3.4.3 |
| julia | OpenEXR_jll | >=3.1.4+0, <3.4.4+0 |
3.4.4+0 |
Affected products
- AcademySoftwareFoundation openexr
Classification
- Weakness
-
- CWE-120 Buffer Copy without Checking Size of Input
References
-
github.com
/AcademySoftwareFoundation/openexr/security/advisories/GHSA-vh63-9mqx-wmjr
exploit, web, vendor-advisory
-
github.com
/AcademySoftwareFoundation/openexr/blob/b3a19903db0672c63055023aa788e592b16ec3c5/src/wrappers/python/PyOpenEXR
web, product
-
nvd.nist.gov
/vuln/detail/CVE-2025-64182
advisory
-
github.com
/AcademySoftwareFoundation/openexr
package
-
pypi.org
/project/openexr
package
-
github.com
/advisories/GHSA-vh63-9mqx-wmjr
advisory
Sources
- CVE List CVE-2025-64182
- GitHub Advisory GHSA-vh63-9mqx-wmjr
- NVD CVE-2025-64182
- OSV JLSEC-2026-138
- OSV PYSEC-2026-2851
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.