dbcve.org
OpenexrApplication

CVE-2026-34544

HIGH · 7.3 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 3.2.7 / 3.3.9 or later.
See remediation →
73/100
Remediation priority · Elevated
Public exploit Patch available

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. From version 3.4.0 to before version 3.4.8, a crafted B44 or B44A EXR file can cause an out-of-bounds write in any application that decodes it via exr_decoding_run(). Consequences range from immediate crash (most likely) to corruption of adjacent heap allocations (layout-dependent). This issue has been patched in version 3.4.8.

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
How this class of weakness works · CWE-190

An arithmetic operation produces a value too large for its type and wraps around to an unexpected — often tiny or negative — number. That miscalculated value then drives a memory allocation or a bounds check, opening the door to corruption. The fix is checked arithmetic and validating sizes before they're used.

General guidance for the integer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.7>= 3.3.0, < 3.3.9>= 3.4.0, < 3.4.8

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

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

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.7 / 3.3.9 / 3.4.8 or later
Fixed in 3.2.73.3.93.4.8
Vendor patch github.com →
Recommended fix High confidence

OpenEXR 3.4.8 (or latest 3.4.x stable release; alternatively 3.2.7 or 3.3.9 depending on your current branch)

  1. 1. Identify the currently installed OpenEXR version using your package manager or build system (e.g., `dpkg -l | grep openexr`, `rpm -qa | grep openexr`, or checking your build configuration).
  2. 2. Update to the appropriate patched version based on your current minor branch: for 3.2.x line upgrade to 3.2.7, for 3.3.x line upgrade to 3.3.9, or for 3.4.x line upgrade to 3.4.8.
  3. 3. Obtain the new version from your distribution's package repository, or rebuild OpenEXR from source using the tagged release (e.g., `git clone https://github.com/AcademySoftwareFoundation/openexr.git && cd openexr && git checkout v3.4.8 && mkdir build && cd build && cmake .. && make -j$(nproc) && make install`).
  4. 4. Rebuild any dependent applications that link against the OpenEXR library to ensure they use the updated version.
  5. 5. Verify the installed version matches the patched release using `exrinfo --version` or equivalent.
Caveat Review release notes for your target version to check for any API/ABI changes that may affect dependent applications

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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