Vulnerability in OpenImageIO (CVE-2026-67549)
Summary
Vulnerability in OpenImageIO (CVE-2026-67549). 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 1-bit contiguous cmyk tiff is exposed through a native uint1 imagespec, so callers allocate a bit-packed buffer. tiffinput::read_native_scanline_locked() nevertheless invokes tiffinput::bit_convert() with 8-bit output and writes one expanded byte per value into that smaller buffer, resulting in a heap out-of-bounds write and memory corruption. The affected implementation is identified by src/tiff.imageio/tiffinput.cpp, TIFFInput::bit_convert(), TIFFInput::read_native_scanline_locked(), PHOTOMETRIC_SEPARATED, 1-bit CMYK, and native uint1 ImageSpec, 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-67549 has been found in OpenImageIO.
Risk of unauthorized operations or information disclosure. CVSS score: 7.6/10.
What to do: upgrade OpenImageIO to 3.1.16.0 or later.
If unsure, ask your IT team or search "OpenImageIO CVE-2026-67549" on the vendor's site.
CVE-2026-67549 (OpenImageIO) — CWE-122 / CVSS v3 7.6
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-122) exists in OpenImageIO.
Check the vendor advisory for the affected versions of OpenImageIO.
Severity: High (CVSS 7.6/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 でアラート再発が無いか継続監視。
References
- exploit security-advisories@github.com
- exploit github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web security-advisories@github.com