CVE-2025-48072: OpenEXR Heap-Based Buffer Overflow Due to Bad Pointer Arithmetic

openexr Updated 14 Dec 2025

Summary

31/07/2025
Yes i
Moderate
6.8

CVE-2025-48072: OpenEXR Out of Bounds Heap Read due to Bad Pointer Arithmetic in LossyDctDecoder_execute. Affects openexr versions >= 3.3.2, < 3.3.3. Fixed in 3.3.3. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

OpenEXR is an open-source high dynamic range (HDR) image file format developed by Industrial Light & Magic (ILM) for visual effects and animation. It is widely used in the film and visual effects industry due to its ability to store a wide range of color data and support for multiple layers and channels. The package is designed for high-performance image processing and is often integrated into various graphics applications. However, it has been found to be vulnerable to a heap-based buffer overflow, which can lead to application crashes and potential data leaks.

Vulnerability Detail

The vulnerability arises from a flaw in the LossyDctDecoder_execute function within the OpenEXRCore library, specifically when decompressing DWAA-packed scan-line EXR files. The issue is caused by incorrect pointer arithmetic, where a __m128i pointer is incremented as if it were a uint16_t pointer. This can lead to out-of-bounds memory access, resulting in a heap-based buffer overflow during read operations. An attacker could exploit this vulnerability to crash the application or potentially leak sensitive information.

How To Fix

Latest published version: 3.5.2 as of 23 Oct 2026

pip install --upgrade "openexr==3.5.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.3.3

This is the first release that contains the fix.

pip install --upgrade "openexr==3.3.3"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. It is recommended to apply the patch as soon as possible.

Conclusion

The OpenEXR package has a critical vulnerability (CVE-2025-48072) that can lead to severe consequences if not addressed. Users are strongly encouraged to update to the latest version to protect their applications from potential exploitation.

See every vulnerability recorded for openexr →

Share this vulnerability

FAQ

CVE-2025-48072 is a vulnerability in the OpenEXR package that allows for a heap-based buffer overflow due to bad pointer arithmetic.

Exploiting this vulnerability can lead to application crashes and potential leakage of sensitive information, such as memory addresses.

Versions prior to 3.3.3 are affected by this vulnerability.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring access to the code or installation.

While there are no specific workarounds, it is crucial to prioritize updating to the patched version as soon as possible to mitigate risks.

Related vulnerabilities

Recent vulnerabilities recorded for openexr.

How To Fix

Latest published version: 3.5.2 as of 23 Oct 2026

pip install --upgrade "openexr==3.5.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

3.3.3

This is the first release that contains the fix.

pip install --upgrade "openexr==3.3.3"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback