dbcve.org
OpenexrApplication

CVE-2026-27622

HIGH · 7.8 CVSS v3.1 Published 2026-03-03
Fix available
A fix is available. Upgrade to 3.2.6 / 3.3.8 or later.
See remediation →
81/100
Remediation priority · High
Public exploit 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 CompositeDeepScanLine::readPixels, per-pixel totals are accumulated in vector<unsigned int> total_sizes for attacker-controlled large counts across many parts, total_sizes[ptr] wraps modulo 2^32. overall_sample_count is then derived from wrapped totals and used in samples[channel].resize(overall_sample_count). Decode pointer setup/consumption proceeds with true sample counts, and write operations in core unpack (generic_unpack_deep_pointers) overrun the undersized composite sample buffer. This vulnerability is fixed in v3.2.6, v3.3.8, and v3.4.6.

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-787

The program writes past the bounds of a buffer, overwriting adjacent memory an attacker can turn to their advantage. Crafted input can overwrite control data and redirect execution. Remediation is validating every index and length before a write, plus modern memory-safety mitigations.

General guidance for the out-of-bounds write 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.6>= 3.3.0, < 3.3.8>= 3.4.0, < 3.4.6

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/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.6 / 3.3.8 / 3.4.6 or later
Fixed in 3.2.63.3.83.4.6
Recommended fix High confidence

Upgrade to the latest fixed version in your current branch: v3.2.6 (for 3.2.x), v3.3.8 (for 3.3.x), or v3.4.6 (for 3.4.x). Prefer v3.4.6 if a major version upgrade is feasible.

  1. Identify the currently installed OpenEXR version using your package manager or by checking the library version (e.g., 'dpkg -l | grep openexr' on Debian/Ubuntu, 'rpm -qa | grep openexr' on RHEL/CentOS, or 'brew info openexr' on macOS)
  2. Determine which version branch you are currently on (3.2.x, 3.3.x, or 3.4.x) by examining the major.minor version number
  3. For systems using the 3.2.x branch, upgrade to version 3.2.6 or later
  4. For systems using the 3.3.x branch, upgrade to version 3.3.8 or later
  5. For systems using the 3.4.x branch, upgrade to version 3.4.6 or later
  6. On Debian/Ubuntu: run 'sudo apt-get update && sudo apt-get install libopenexr-dev' or 'sudo apt-get upgrade libopenexr-dev'
  7. On RHEL/CentOS/Fedora: run 'sudo dnf update openexr' or 'sudo yum update openexr'
  8. On macOS with Homebrew: run 'brew upgrade openexr'
Caveat Review the release notes for the intermediate versions between your current version and the target fixed version to check for any API/ABI changes or backward-incompatible changes that may affect your application.

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-27622 — 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-27622 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