NVD / CVE Program· CNA GitHub_M

CVE-2025-64182: OpenEXR has buffer overflow in PyOpenEXR_old's channels() and channel()

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: openexr (openSUSE:Tumbleweed) 3.4.3-1.1; openexr (PyPI) 3.2.5, 3.3.6, 3.4.3.

Low priority for now. Upgrade to openexr (openSUSE:Tumbleweed) 3.4.3-1.1; openexr (PyPI) 3.2.5, 3.3.6, 3.4.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v4.0—No exploit Fix available

Memory safety

Published: Nov 10, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 17th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 5.5; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
openexr	openexr	cpe:2.3:a:openexr:openexr

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

openexr openexr3.2.0 and later · before 3.2.5
openexr openexr3.3.0 and later · before 3.3.6
openexr openexr3.4.0 and later · before 3.4.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

AcademySoftwareFoundation openexr
- >= 3.2.0, < 3.2.5, >= 3.3.0, < 3.3.6, >= 3.4.0, < 3.4.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
openSUSE:Tumbleweed	openexr	before 3.4.3-1.1	3.4.3-1.1
PyPI	openexr	from 3.2.0 · before 3.2.5	3.2.5
PyPI	openexr	from 3.3.0 · before 3.3.6	3.3.6
PyPI	openexr	from 3.4.0 · before 3.4.3	3.4.3

Same product

openexr: all records

Other highest-scoring records for the same primary product.

CVE-2023-5841OpenEXR Heap Overflow in Scanline Deep Data Parsing
36Monitor
CVE-2021-23169A heap-buffer overflow was found in the copyIntoFrameBuffer function of OpenEXR in versions before 3.0.1.
36Monitor
CVE-2017-9115In OpenEXR 2.2.0, an invalid write of size 2 in the = operator function in half.h could cause the application to crash or execute arbitrary
36Monitor

Published before and after this one in the same product

← EarlierCVE-2025-48074Aug 1, 2025 · OpenEXR's Unbounded File Header Values can Lead to Out-Of-Memory Errors
18Monitor
← EarlierCVE-2025-64181Nov 10, 2025 · OpenEXR Makes Use of Uninitialized Memory
8Monitor
Later →CVE-2025-64183Nov 10, 2025 · OpenEXR has use after free in PyObject_StealAttrString
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
opensuse:openexr	3.4.3-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
PyPI:openexr	3.2.5	Package registry (OSV)
PyPI:openexr	3.3.6	Package registry (OSV)
PyPI:openexr	3.4.3	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Local
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

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-secondary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/AcademySoftwareFoundation/openexr/blob/b3a19903db0672c63055023aa788e592b16ec3c5/src/wrappers/python/PyOpenEXR_old.cpp#L528-L536

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records