dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-59731

MEDIUM · 6.9 CVSS v4.0 Published 2025-10-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
When decoding an OpenEXR file that uses DWAA or DWAB compression, the specified raw length of run-length-encoded data is not checked when using it to calculate the output data. We read rle_raw_size from the input file at [0], we decompress and decode into the buffer td->rle_raw_data of size rle_raw_size at [1], and then at [2] we will access entries in this buffer up to (td->xsize - 1) * (td->ysize - 1) + rle_raw_size / 2, which may exceed rle_raw_size. We recommend upgrading to version 8.0 or beyond.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenEXR fails to validate the raw length of run-length-encoded data when decoding DWAA or DWAB compressed files. The rle_raw_size value from the file is used directly to allocate a buffer, but subsequent buffer access calculations ((td->xsize - 1) * (td->ysize - 1) + rle_raw_size / 2) can exceed the allocated rle_raw_size, causing a heap buffer overflow during decompression.

MitigationUpgrade OpenEXR to version 8.0 or later, which contains the fix for proper bounds validation of RLE data lengths before decompression.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
High
Privileges
Low
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:A/AC:H/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if OpenEXR library is installed
    Run 'pkg-config --modversion OpenEXR' or check your package manager for the installed openexr package version
    Affected if OpenEXR is installed with a version lower than 8.0.0
  2. Verify OpenEXR version number
    Use 'openexrversion' command if available, or check the shared library version with 'ldd' or 'dpkg -l | grep openexr'
    Affected if The installed version is earlier than 8.0 (the fixed release)
  3. Identify if DWAA or DWAB compression is in use
    Inspect your OpenEXR files using 'exrheader' or 'exrinfo' tools to check the 'compression' attribute
    Affected if The compression field shows 'DWAA' or 'DWAB' compression, which are the formats that trigger the vulnerable code path
  4. Check for untrusted .exr file processing
    Review application logs or code that decodes OpenEXR files to see if it processes files from untrusted sources
    Affected if The application decodes OpenEXR files with DWAA/DWAB compression from sources outside your trust boundary (such as user uploads, network sources, or untrusted datasets)

You are affected if OpenEXR version is below 8.0 AND your environment processes OpenEXR files using DWAA or DWAB compression from potentially untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenEXR to version 8.0 or later, which contains the fix for proper bounds validation of RLE data lengths before decompression.

Recommended fix High confidence

OpenEXR 8.0 or later

  1. 1. Identify the OpenEXR library version currently in use by your project (check package.json, requirements.txt, CMakeLists.txt, or package manager dependencies)
  2. 2. Update the OpenEXR dependency to version 8.0 or later using your package manager (e.g., pip install openexr>=8.0, conda install openexr>=8.0, or apt-get install libopenexr-dev>=8.0)
  3. 3. Rebuild and recompile any projects that link against the OpenEXR library
  4. 4. Verify the upgrade by running your application's test suite, particularly any tests involving OpenEXR file loading
  5. 5. Ensure the new library version is deployed to all production environments
Caveat Major version upgrades may introduce API changes; review OpenEXR 8.0 release notes for any breaking changes to decompression functions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59731 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59731 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data