dbcve.org
OpenexrApplication

CVE-2026-40244

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:1722` performs `curc->width * curc->height` in `int32` arithmetic without a `(size_t)` cast. This is the same overflow pattern fixed in other locations by the recent CVE-2026-34589 batch, 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:1722`.

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

Integer overflow vulnerability in OpenEXR's DWA compressor where `curc->width * curc->height` is computed using 32-bit int arithmetic without a (size_t) cast at internal_dwa_compressor.h:1722. This can cause the multiplication result to overflow, potentially leading to heap corruption or denial of service when processing specially crafted EXR image files.

MitigationUpgrade OpenEXR to version 3.4.10, 3.3.10, or 3.2.8 which contain the fix for this integer overflow by adding the proper (size_t) cast.

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. Determine OpenEXR library version
    Run `pkg-config --modversion OpenEXR` or check the library file with `dpkg -l | grep openexr` (Debian) or `rpm -q openexr` (RHEL). If built from source, check the version in the source directory or the installed headers.
    Affected if The installed version is 3.2.0 through 3.2.7, 3.3.0 through 3.3.9, or 3.4.0 through 3.4.9 (i.e., it falls within any of the affected ranges: >=3.2.0 <3.2.8, >=3.3.0 <3.3.10, or >=3.4.0 <3.4.10).
  2. Identify if any EXR files use DWA compression
    Use `exrinfo -c <file.exr>` or examine the compression method field in the EXR file header. DWA compression appears as DWAA (lossy) or DWAB (lossy with higher quality) in the compression attribute.
    Affected if EXR files processed by the OpenEXR library use DWAA or DWAB compression, as the vulnerability exists specifically in the DWA compressor code path.
  3. Verify the vulnerable code path is reachable
    Check if any application or tool loads and processes EXR files with DWA compression. This includes image viewers, editors, or custom tools using libOpenEXR to decode EXR images.
    Affected if Any application linked against the affected OpenEXR version is used to process DWA-compressed EXR files, triggering the integer overflow at internal_dwa_compressor.h:1722.

You are affected if your installed OpenEXR version is within any of the affected ranges AND you process EXR files using DWAA or DWAB compression, as the overflow occurs in the DWA compressor when computing width*height without a size_t cast.

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 which contain the fix for this integer overflow by adding the proper (size_t) cast.

Recommended fix High confidence

OpenEXR 3.2.8 (or later 3.2.x), 3.3.10 (or later 3.3.x), or 3.4.10 (or later 3.4.x)

  1. Identify the current OpenEXR version in use (e.g., via package manager or binary inspection)
  2. Determine which version branch is in use (3.2.x, 3.3.x, or 3.4.x)
  3. Upgrade to the fixed version for that branch: 3.2.8 for 3.2.x, 3.3.10 for 3.3.x, or 3.4.10 for 3.4.x
  4. Verify the upgrade was successful by checking the new version number
  5. Rebuild any dependent projects or applications that link against OpenEXR

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

Fix this in Openexr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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