Vulnerability in OpenImageIO (CVE-2026-65970)
Summary
Vulnerability in OpenImageIO (CVE-2026-65970). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.1.16.0 or later.
Original description
The description as published by the source.
OpenImageIO is a toolset for reading, writing, and manipulating image files of any image file format relevant to VFX / animation. Prior to 3.1.16.0, a crafted ZIP-compressed TIFF processed with TIFF multithreading enabled can make TIFFInput::read_native_scanlines() return through an error path while asynchronous strip-decompression work remains queued. Because task_set is declared before ok and compressed_scratch, those captured objects are destroyed before the task-set destructor waits, allowing worker tasks to use stale stack and heap storage, resulting in a use-after-scope crash and denial of service. The affected implementation is identified by src/tiff.imageio/tiffinput.cpp, TIFFInput::read_native_scanlines(), task_set, ok, compressed_scratch, and uncompress_one_strip(), which define the relevant source path, functions, state, and trigger. This issue is fixed in 3.1.16.0.
Source: NIST National Vulnerability Database NVD
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 CVE-2026-65970 has been found in OpenImageIO.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade OpenImageIO to 3.1.16.0 or later.
If unsure, ask your IT team or search "OpenImageIO CVE-2026-65970" on the vendor's site.
CVE-2026-65970 (OpenImageIO) — CWE-825 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Patched: 3.1.16.0 — 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 (CWE-825) exists in OpenImageIO.
Check the vendor advisory for the affected versions of OpenImageIO.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 3.1.16.0.
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 'OpenImageIO' . 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
-
1Identify exposure identify
grep -r 'OpenImageIO' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OpenImageIOを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade OpenImageIO to 3.1.16.0ステージング環境で 3.1.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-65970 openimageio
References
- exploit github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web security-advisories@github.com