dbcve.org
OpenexrApplication

CVE-2026-40250

HIGH · 7.1 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to 3.2.8 / 3.3.10 or later.
See remediation →
74/100
Remediation priority · Elevated
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
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In versions 3.4.0 through 3.4.9, 3.3.0 through 3.3.9, and 3.2.0 through 3.2.7, `internal_dwa_compressor.h:1040` performs `chan->width * chan->bytes_per_element` in `int32` arithmetic without a `(size_t)` cast. This is the same overflow pattern fixed in other decoders by CVE-2026-34589/34588/34544, but this line was missed. Versions 3.4.10, 3.3.10, and 3.2.8 contain a fix that addresses `internal_dwa_compressor.h:1040`.

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 contains an integer overflow vulnerability in the DWA compressor at internal_dwa_compressor.h:1040. The code performs width * bytes_per_element calculation using int32 arithmetic without a size_t cast, allowing potential buffer overflow when processing specially crafted EXR image files with large dimensions. This is the same overflow pattern previously fixed in CVE-2026-34589/34588/34544 but missed in this code path.

MitigationUpgrade OpenEXR to version 3.4.10, 3.3.10, or 3.2.8 (or later) which contain the fix. Alternatively, apply the size_t cast to the multiplication at line 1040 of internal_dwa_compressor.h.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenexrApplication
Affected:>= 3.2.0, < 3.2.8>= 3.3.0, < 3.3.10>= 3.4.0, < 3.4.10

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

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 OpenEXR installation and version
    Run 'openexrversion' or check package manager (dpkg -l | grep openexr, rpm -qa | grep openexr)
    Affected if Version is >= 3.2.0 and < 3.2.8, OR >= 3.3.0 and < 3.3.10, OR >= 3.4.0 and < 3.4.10
  2. Locate the vulnerable source file
    Find internal_dwa_compressor.h in the source tree or installed headers (find /usr -name internal_dwa_compressor.h 2>/dev/null)
    Affected if File exists at expected path
  3. Inspect the vulnerable code at line 1040
    Open internal_dwa_compressor.h and examine line 1040 for the multiplication width * bytes_per_element
    Affected if The multiplication uses int32 (int) rather than size_t cast, indicating the vulnerability is present
  4. Check if DWA compression support is built
    Check binary/library for DWA compressor linked in (ldd /path/to/libIex.so 2>/dev/null | grep -i openexr) or review build configuration
    Affected if OpenEXR with DWA support is in use and version falls in affected range

A system is affected if OpenEXR version is within any of the three vulnerable ranges AND the DWA compressor code path exists without the size_t cast fix.

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
Upgrade available Upgrade to 3.2.8 / 3.3.10 / 3.4.10 or later
Fixed in 3.2.83.3.103.4.10
Interim mitigation

Upgrade OpenEXR to version 3.4.10, 3.3.10, or 3.2.8 (or later) which contain the fix. Alternatively, apply the size_t cast to the multiplication at line 1040 of internal_dwa_compressor.h.

Recommended fix High confidence

OpenEXR 3.2.8, 3.3.10, or 3.4.10 (select based on current branch)

  1. Identify the current OpenEXR version in use by checking project dependencies or running pkg-config --modversion OpenEXR
  2. Determine which version branch is in use (3.2.x, 3.3.x, or 3.4.x)
  3. Upgrade to the corresponding fixed release: 3.2.8 for 3.2.x branches, 3.3.10 for 3.3.x branches, or 3.4.10 for 3.4.x branches
  4. Update the dependency in the project's build system (e.g., CMake, conan, vcpkg) to specify the minimum fixed version
  5. Rebuild the project to link against the upgraded OpenEXR library
  6. Verify the upgrade was successful by checking that the linked library version matches the target fixed version

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

Fix this in Openexr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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