dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2026-42450

HIGH · 8.4 CVSS v4.0 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
No privileges 8 weeks old

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 · unedited
OpenColorIO is a color management framework for visual effects and animation. Prior to version 2.5.2, `FileFormatSpi3D.cpp:163` uses `sscanf` with `%s` into 64-byte stack buffers when parsing LUT data lines. Input comes from `lineBuffer[4096]`, so a crafted .spi3d file can overflow by ~4000 bytes on non-Windows. Version 2.5.2 fixes the issue.

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 confidence

OpenColorIO prior to 2.5.2 has a stack-based buffer overflow in FileFormatSpi3D.cpp where sscanf with %s reads into 64-byte fixed-size buffers from a 4096-byte lineBuffer, allowing a crafted .spi3d LUT file to overflow by approximately 4000 bytes on non-Windows systems.

MitigationUpgrade OpenColorIO to version 2.5.2 or later to obtain the patched version. Until then, avoid processing untrusted .spi3d files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenColorIO installation and version
    Run 'ocioversion' or 'ocioconf --version' from command line, or check library binary with 'strings' grep for version string like '2.5.1' or '2.5.0'
    Affected if Version is present and lower than 2.5.2 (e.g., 2.5.1, 2.5.0, 2.4.x, 2.3.x, etc.)
  2. Confirm operating system is non-Windows
    Run 'uname -s' or check system documentation - this vulnerability only affects non-Windows systems (Linux, macOS, etc.)
    Affected if Operating system is Linux, macOS, or other Unix-like system (NOT Windows)
  3. Check if .spi3d file processing is in use
    Search project/codebase for FileFormatSpi3D usage, or inspect configuration files referencing .spi3d LUT files, or check application logs for spi3d loader activity
    Affected if The application or tool loads or parses .spi3d LUT files using OpenColorIO
  4. Verify the vulnerable code path is reachable
    Review application behavior to confirm the FileFormatSpi3D parser is invoked when loading .spi3d files - this is the component with the sscanf buffer overflow
    Affected if The OpenColorIO library parses .spi3d files through the FileFormatSpi3D component

You are affected if OpenColorIO version is lower than 2.5.2 AND you run on a non-Windows system AND your application processes .spi3d LUT files using OpenColorIO's FileFormatSpi3D parser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenColorIO to version 2.5.2 or later to obtain the patched version. Until then, avoid processing untrusted .spi3d files.

Recommended fix High confidence

OpenColorIO 2.5.2

  1. 1. Identify the current OpenColorIO version in use by checking the project's dependencies or build configuration (e.g., package.json, CMakeLists.txt, conanfile.txt, or pip/conda package list).
  2. 2. Locate all .spi3d file parsing code that uses FileFormatSpi3D.cpp and verify it is linked against the identified OpenColorIO version.
  3. 3. Upgrade OpenColorIO to version 2.5.2 or later by updating the dependency specification in your project's package manager (e.g., change version constraint to '>=2.5.2' in requirements.txt, package.json, or similar).
  4. 4. Rebuild and redeploy the application to ensure the fixed OpenColorIO library is used.
  5. 5. Validate that .spi3d file processing still functions correctly with the updated library by testing with known-good .spi3d LUT files.
Caveat No breaking changes are expected for this security patch upgrade; version 2.5.2 is a maintenance release fixing the buffer overflow vulnerability.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42450 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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