CVE-2025-48071 OpenEXR's Forged Unpacked Size can Lead to Heap-Based Buffer Overflow in Deep Scanline Parsing

High 8.4 Published Updated

A heap-based buffer overflow in OpenEXR allows attackers to execute arbitrary code or cause denial of service via maliciously crafted EXR files.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2025-48071?

CVE-2025-48071 is a high-severity memory corruption vulnerability in Openexr Openexr, published on 31 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official 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.2 through 3.3.0, there is a heap-based buffer overflow during a write operation when decompressing ZIPS-packed deep scan-line EXR files with a maliciously forged chunk header. This is fixed in version 3.3.3.

Weakness: CWE-122

Which versions are affected by CVE-2025-48071?

3 open source packages ship an affected version, including openexr and OpenEXR. It affects 1 product.

PackageAffectedFixed in
openexr PyPIFrom 3.3.03.3.3
openexr PyPIFrom 3.3.03.3.3
OpenEXR PyPIFrom 3.3.03.3.3

Products include Openexr Openexr.

How do I fix CVE-2025-48071?

Upgrade openexr to 3.3.3 or later.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2025-48071 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48071 exists.

All Openexr Openexr vulnerabilities

Sources

Also known as GHSA-h45x-qhg2-q375, PYSEC-2026-1747.

Is CVE-2025-48071 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free