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

CVE-2025-59732

HIGH · 8.7 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 →
90/100
Remediation priority · Urgent
No privileges

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, there's an implicit assumption that the height and width are divisible by 8. If the height or width of the image is not divisible by 8, the copy loops at [0] and [1] will continue to write until the next multiple of 8. The buffer td->uncompressed_data is allocated in decode_block based on the precise height and width of the image, so the "rounded-up" multiple of 8 in the copy loop can exceed the buffer bounds, and the write block starting at [2] can corrupt following heap memory. 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

A heap buffer overflow vulnerability exists in OpenEXR's DWAA/DWAB decompression. When decoding OpenEXR files with dimensions not divisible by 8, the copy loops round up to the next multiple of 8 and write beyond the bounds of the buffer allocated for the exact image dimensions, causing heap memory corruption.

MitigationUpgrade OpenEXR to version 8.0 or later. Review any custom code that parses or decodes OpenEXR files to ensure it handles non-8-divisible dimensions correctly.

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
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:A/AC:H/AT:N/PR:N/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. Identify installed OpenEXR version
    Run 'openexrversion' or check library version via 'ldd' on any binary using OpenEXR, or inspect the package manager output (dpkg -l libopenexr*, rpm -qi OpenEXR, brew list openexr)
    Affected if version is lower than 8.0
  2. Confirm DWAA or DWAB compression is in use
    Inspect OpenEXR file headers using 'exrheader' or similar tool to check the 'compression' attribute, or review application code that loads OpenEXR files for DWAA/DWAB compression setting
    Affected if files use DWAA or DWAB compression schemes
  3. Identify files with non-8-divisible dimensions
    Use 'exrheader' or exrinfo tool to examine 'dataWindow' or image dimensions (width and height). Calculate width % 8 and height % 8 for each file.
    Affected if any loaded .exr files have width or height not divisible by 8 while using DWAA/DWAB compression
  4. Check for heap corruption indicators
    Run the application with memory debugging tools (AddressSanitizer, Valgrind) or check system logs/dmesg for heap-related errors when processing suspect files
    Affected if memory errors or crashes occur when decoding DWAA/DWAB files with non-8-divisible dimensions

You are affected if OpenEXR version is below 8.0 AND you process DWAA or DWAB compressed files with dimensions not divisible by 8.

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. Review any custom code that parses or decodes OpenEXR files to ensure it handles non-8-divisible dimensions correctly.

Recommended fix High confidence

OpenEXR version 8.0 or later

  1. Identify the current OpenEXR version in use by checking project dependencies or system packages
  2. Consult the OpenEXR release notes for version 8.0 to understand changes and migration requirements
  3. Use the appropriate package manager or build system to upgrade OpenEXR to version 8.0 or later (e.g., 'pip install openexr>=8.0', 'conda install openexr>=8.0', or rebuild from source)
  4. Verify the upgrade was successful by checking the installed version
  5. Rebuild and test any applications that depend on OpenEXR to ensure compatibility
Caveat Review OpenEXR 8.0 release notes for any API changes or breaking changes that may affect existing code

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59732 — 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-59732 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