Quick answers
- Is CVE-2025-48074 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-48074 being exploited in the wild.
- How severe is CVE-2025-48074?
- Medium severity, with a CVSS score of 4, published 31 July 2025.
- Which products and versions are affected?
- OpenEXR (PyPI) = 3.3.2, ECOSYSTEM:introduced=3.3.2,fixed=3.3.3.
- Is there a fix for CVE-2025-48074?
- Yes. OpenEXR (PyPI): upgrade to 3.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-48074 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2025-48074?
- Check whether you run OpenEXR (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- OpenEXR (PyPI): upgrade to 3.3.3 or later
pip install "OpenEXR>=3.3.3"
Technical details
A resource exhaustion vulnerability (CWE-770) exists in OpenEXR version 3.3.2 due to improper validation of 'dataWindow' values in image headers. The library trusts these values to perform computations and memory allocations, specifically in functions like readScanline() and EnvmapImage::resize(). An attacker can provide a crafted EXR file with extreme dataWindow coordinates to trigger excessive loop iterations or multi-gigabyte memory allocations, leading to application crashes (std::bad_alloc) or system-wide memory exhaustion. The issue is addressed in version 3.3.3.
Affected products
- AcademySoftwareFoundation OpenEXR 3.3.2
Identifiers
- CVE-2025-48074
- GHSA-x22w-82jp-8rvf
- PYSEC-2026-1749
Timeline
- 2025-07-31: disclosed
- 2025-07-31: advisory
- 2025-07-31: patched: Fixed in version 3.3.3