Quick answers
- Is CVE-2026-63638 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63638 being exploited in the wild.
- How severe is CVE-2026-63638?
- High severity, with a CVSS score of 8.3, published 18 September 2026.
- Which products and versions are affected?
- Academy Software Foundation OpenImageIO prior to 3.0.21.0, 3.1.16.0, and 3.2.0.3-beta1.
- Is there a fix for CVE-2026-63638?
- A patch was published on 2026-07-06: Fix merged in commit 6f2b2e8 to validate bit depth against libcineon's supported set Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63638 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63638?
- Check whether you run Academy Software Foundation OpenImageIO at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A mismatch between OpenImageIO's bit-depth validation (accepting 1–32) and libcineon's supported depths (only 8, 10, 12, 16, 32, 64) allows a crafted cineon file with an unsupported depth like 26 to pass initial checks and cause a heap out-of-bounds write in CineonInput::read_native_scanline(), when attacker-controlled data is written beyond the caller-allocated 4-byte-per-pixel buffer. The fix tightens validation to reject unsupported bit depths before calling the vulnerable libcineon code.
Affected products
- Academy Software Foundation OpenImageIO prior to 3.0.21.0, 3.1.16.0, and 3.2.0.3-beta1
Timeline
- 2026-09-18: disclosed: CVE-2026-63638 published
- 2026-07-06: patched: Fix merged in commit 6f2b2e8 to validate bit depth against libcineon's supported set