Vulnerability in openexr (UBUNTU-CVE-2026-27622)

Summary

Vulnerability in openexr (UBUNTU-CVE-2026-27622). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.2.6 or later.

Original description

The description as published by the source.

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

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-27622 has been found in openexr.
Successful exploitation can lead to full system takeover.
What to do: upgrade openexr to 3.2.6 or later.
If unsure, ask your IT team or search "openexr UBUNTU-CVE-2026-27622" on the vendor's site.

UBUNTU-CVE-2026-27622 (openexr)
Attack vector: local / unauthenticated
Patched: 3.2.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in openexr.

📍 Affected scope

Check the vendor advisory for the affected versions of openexr.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.2.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openexr' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'openexr' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で openexr を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade openexr to 3.2.6
```
ステージング環境で 3.2.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:16.04:LTS openexr

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.0-10ubuntu2.6+esm4"}]}]

Ubuntu:Pro:18.04:LTS openexr

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.0-11.1ubuntu1.9+esm1"}]}]

Ubuntu:Pro:20.04:LTS openexr

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.0-6ubuntu0.5+esm2"}]}]

Ubuntu:Pro:22.04:LTS openexr

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.5.7-1ubuntu0.1~esm2"}]}]

Ubuntu:Pro:24.04:LTS openexr

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.5-5.1ubuntu0.1~esm1"}]}]

Ubuntu:25.10 openexr

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:26.04:LTS openexr

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.13-2ubuntu0.26.04.1~esm1"}]}]

References

advisory ubuntu.com
report ubuntu.com
report cve.org
report github.com