CVE-2026-43903
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenImageIO 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenImageIO contains a heap buffer overflow vulnerability in the SGI image file parser (sgiinput.cpp). The RLE decode loop uses OIIO_DASSERT for bounds checking, but in release builds these assertions compile to no-ops, allowing a crafted .sgi file with RLE count exceeding scanline width to overflow the heap and cause a crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.0.18.0>= 3.1.4.0, < 3.1.13.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine OpenImageIO library versionRun 'oiioinfo --version' or check package manager (dpkg -l libopenimageio, rpm -q libopenimageio, brew list openimageio)Affected if Version is less than 3.0.18.0 OR (version >= 3.1.4.0 AND version < 3.1.13.0)
-
Identify tools using OpenImageIOCheck for installed tools that link to OpenImageIO: 'ldd $(which oiiotool imageinfo) 2>/dev/null | grep -i openimageio' or 'dpkg -l | grep -i oiio'Affected if OpenImageIO-based image tools are installed on the system
-
Verify SGI file support is presentRun 'oiioinfo --formatlist 2>/dev/null | grep -i sgi' or 'file some.sgi' to confirm SGI format can be readAffected if SGI format support is available in the OpenImageIO build
-
Check for untrusted .sgi file processingAudit workflows, scripts, or services that process .sgi image files from external or untrusted sourcesAffected if The environment processes .sgi files from untrusted or external sources using OpenImageIO-based tools
A user is affected if OpenImageIO version falls within the vulnerable ranges (< 3.0.18.0 or >= 3.1.4.0 to < 3.1.13.0) AND the system processes .sgi files, particularly from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.0.18.03.1.13.0
Upgrade OpenImageIO to version 3.0.18.0 or 3.1.13.0 or later. Until upgraded, do not process untrusted .sgi files with OpenImageIO-based tools.
OpenImageIO 3.0.18.0 or 3.1.13.0 (depending on your current major version branch)
- 1. Identify the currently installed OpenImageIO version using your package manager or build system (e.g., 'pip show OpenImageIO', 'dpkg -l libopenimageio', or checking CMakeLists.txt)
- 2. If using version < 3.0.18.0, plan upgrade to version 3.0.18.0
- 3. If using version >= 3.1.4.0 and < 3.1.13.0, plan upgrade to version 3.1.13.0
- 4. For package manager installations: run 'pip install --upgrade OpenImageIO' or your distribution's equivalent upgrade command
- 5. For source builds: download the appropriate tag (v3.0.18.0 or v3.1.13.0) from the OpenImageIO GitHub repository and rebuild
- 6. Verify the upgrade was successful by checking the installed version matches the target fixed release
- 7. Test image processing workflows with .sgi files to confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43903 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-43903 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data