CVE-2026-42450

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.4
EG Score
8.4(medium)
EPSS
2.1%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

Stack buffer overflow via unbounded `sscanf %s` in Spi3D (.spi3d) LUT parser · Advisory · AcademySoftwareFoundation/OpenColorIO · GitHub

https://github.com/AcademySoftwareFoundation/OpenColorIO/security/advisories/GHSA-rxp3-rrgx-f547
github_release Patch Available

v2.5.2

Patch available: AcademySoftwareFoundation/OpenColorIO v2.5.2

https://github.com/AcademySoftwareFoundation/OpenColorIO/releases/tag/v2.5.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 66× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 20:01 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 08:45 UTCEG score recompute
  4. 2026-07-14 21:22 UTCEG score recompute
  5. 2026-07-14 10:06 UTCEG score recompute
  6. 2026-07-13 22:49 UTCEG score recompute
  7. 2026-07-13 22:30 UTCEPSS rescore
  8. 2026-07-13 11:33 UTCEG score recompute
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 00:17 UTCEG score recompute
  11. 2026-07-12 13:00 UTCEG score recompute
  12. 2026-07-12 01:44 UTCEG score recompute
  13. 2026-07-11 14:27 UTCEG score recompute
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 03:11 UTCEG score recompute
  16. 2026-07-10 15:48 UTCEG score recompute
  17. 2026-07-10 04:26 UTCEG score recompute
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 17:06 UTCEG score recompute
  20. 2026-07-09 05:50 UTCEG score recompute
  21. 2026-07-08 18:34 UTCEG score recompute
  22. 2026-07-08 15:15 UTCEPSS rescore
  23. 2026-07-08 07:18 UTCEG score recompute
  24. 2026-07-07 19:45 UTCEG score recompute
  25. 2026-07-07 13:46 UTCEPSS rescore
Show 41 more
  1. 2026-07-07 08:28 UTCEG score recompute
  2. 2026-07-06 21:11 UTCEG score recompute
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 09:50 UTCEG score recompute
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 22:32 UTCEG score recompute
  9. 2026-07-05 11:16 UTCEG score recompute
  10. 2026-07-04 23:59 UTCEG score recompute
  11. 2026-07-04 12:44 UTCEG score recompute
  12. 2026-07-04 01:27 UTCEG score recompute
  13. 2026-07-03 14:12 UTCEG score recompute
  14. 2026-07-03 02:55 UTCEG score recompute
  15. 2026-07-02 15:39 UTCEG score recompute
  16. 2026-07-02 04:23 UTCEG score recompute
  17. 2026-07-01 17:06 UTCEG score recompute
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-07-01 05:51 UTCEG score recompute
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 18:32 UTCEG score recompute
  22. 2026-06-30 07:16 UTCEG score recompute
  23. 2026-06-29 20:00 UTCEG score recompute
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 08:44 UTCEG score recompute
  26. 2026-06-28 21:27 UTCEG score recompute
  27. 2026-06-28 14:07 UTCEPSS rescore
  28. 2026-06-28 10:11 UTCEG score recompute
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-27 22:55 UTCEG score recompute
  31. 2026-06-27 11:39 UTCEG score recompute
  32. 2026-06-27 03:08 UTCEPSS rescore
  33. 2026-06-27 00:23 UTCEG score recompute
  34. 2026-06-26 13:07 UTCEG score recompute
  35. 2026-06-26 01:50 UTCEG score recompute
  36. 2026-06-25 14:34 UTCEG score recompute
  37. 2026-06-25 13:49 UTCEPSS rescore
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-25 03:18 UTCEG score recompute
  40. 2026-06-24 16:02 UTCEG score recompute
  41. 2026-06-24 16:02 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-42450?
CVE-2026-42450 is a high vulnerability published on June 24, 2026. 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…
When was CVE-2026-42450 disclosed?
CVE-2026-42450 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42450 actively exploited?
CVE-2026-42450 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42450?
CVE-2026-42450 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-42450?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42450, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42450

Explore →

Is Your Infrastructure Affected by CVE-2026-42450?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.