Vulnerability in openexr
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-34380 has been found in openexr.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openexr to 3.2.7 or later.
If unsure, ask your IT team or search "openexr UBUNTU-CVE-2026-34380" on the vendor's site.
UBUNTU-CVE-2026-34380 (openexr)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 3.2.7 — 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.
A vulnerability (unclassified) exists in openexr.
Check the vendor advisory for the affected versions of openexr.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.2.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 exposureidentify
grep -r 'openexr' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openexrを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade openexr to 3.2.7ステージング環境で 3.2.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Ubuntu:Pro:24.04:LTS | openexr |
< 3.1.5-5.1ubuntu0.1~esm1 |
3.1.5-5.1ubuntu0.1~esm1 |
| Ubuntu:25.10 | openexr |
All versions |
— |
| Ubuntu:Pro:26.04:LTS | openexr |
< 3.1.13-2ubuntu0.26.04.1~esm1 |
3.1.13-2ubuntu0.26.04.1~esm1 |
| Ubuntu:26.10 | openexr |
All versions |
— |
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. From 3.2.0 to before 3.2.7, 3.3.9, and 3.4.9, a signed integer overflow exists in undo_pxr24_impl() in src/lib/OpenEXRCore/internal_pxr24.c at line 377. The expression (uint64_t)(w * 3) computes w * 3 as a signed 32-bit integer before casting to uint64_t. When w is large, this multiplication constitutes undefined behavior under the C standard. On tested builds (clang/gcc without sanitizers), two's-complement wraparound commonly occurs, and for specific values of w the wrapped result is a small positive integer, which may allow the subsequent bounds check to pass incorrectly. If the check is bypassed, the decoding loop proceeds to write pixel data through dout, potentially extending far beyond the allocated output buffer. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report github.com
- report github.com
- report github.com
- report github.com
- report github.com
- report github.com
- report github.com
- report github.com