Out-of-Bounds Write in OpenImageIO (CVE-2026-43903)
Summary
Out-of-bounds write in OpenImageIO (CVE-2026-43903). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.0.18.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.0.18.0 and 3.1.13.0, sgiinput.cpp:265,274 use OIIO_DASSERT for bounds checking in the RLE decode loop. In release builds, OIIO_DASSERT compiles to ((void)sizeof(x)) (dassert.h:210), making all bounds checks no-ops. A crafted .sgi file with RLE count exceeding scanline width causes heap buffer overflow and crash. This vulnerability is fixed in 3.0.18.0 and 3.1.13.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-43903 has been found in OpenImageIO.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade OpenImageIO to 3.0.18.0 or later.
If unsure, ask your IT team or search "OpenImageIO CVE-2026-43903" on the vendor's site.
CVE-2026-43903 (OpenImageIO) — CWE-787 / CVSS v3 7.8
Attack vector: local / unauthenticated
Patched: 3.0.18.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.
Out-of-bounds write (CWE-787) exists in OpenImageIO.
Check the vendor advisory for the affected versions of OpenImageIO.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 3.0.18.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.0.18.0ステージング環境で 3.0.18.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
- Debian DEBIAN-CVE-2026-43903 openimageio
- Ubuntu UBUNTU-CVE-2026-43903 openimageio
References
- patch github.com