CVE-2026-63419
CVE-2026-63419 — OpenImageIO: IFF ZBUFFER tile read writes past caller tile buffer
OpenImageIO is a toolset for reading, writing, and manipulating image files of any image file format relevant to VFX / animation. Prior to 3.0.21.0, 3.1.16.0, and 3.2.0.3-beta1, A zbuffer-only tiled iff is exposed with a 16-bit public imagespec while the decoder retains a 32-bit internal pixel size. iffinput::read_native_tile() copies according to m_header.pixel_bytes() rather than imagespec::tile_bytes(true), and a failed read can leave m_buf nonempty so a later call copies partially initialized data into the undersized caller buffer, resulting in a heap out-of-bounds write and memory corruption. The affected implementation is identified by src/iff.imageio/iffinput.cpp, IffInput::read_native_tile(), ImageSpec::tile_bytes(true), m_header.pixel_bytes(), ZBUFFER, and m_buf, which define the relevant source path, functions, state, and trigger. This issue is fixed in versions 3.0.21.0, 3.1.16.0, and 3.2.0.3-beta1.
Published Updated Sources: NVD, AcademySoftwareFoundation (CNA), GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
7.8
high
Remediation
The vendor's own words where we have them.
Upgrade OpenImageIO to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| AcademySoftwareFoundation | OpenImageIO | < 3.0.21.0 | Vulnerable |
| AcademySoftwareFoundation | OpenImageIO | >= 3.1.0.0, < 3.1.16.0 | Vulnerable |
| AcademySoftwareFoundation | OpenImageIO | >= 3.2.0.0-dev, < 3.2.0.3-beta1 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
High
Integrity
High
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Local
Privileges Req
None
User Interaction
Required
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | high | 1.8 | 5.9 | GitHub (CNA), AcademySoftwareFoundation (CNA) |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-787 · Out-of-bounds Write
- Modify Memory
- DoS: Crash, Exit, or Restart
- Execute Unauthorized Code or Commands::
Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
Weakness & attack patterns
- CWE-787Out-of-bounds Write
Inferred from the weakness class — not observed against this CVE.
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /iff.imageio/iffinput.cpp.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 7.8 (AV:L)
Sep 18, 2026 · NVD
Initial · CVE published
Sep 18, 2026 · NVD
CVE published by MITRE.
Sep 18, 2026 · SOCRadar CTI
References
5 on the record
- github.com/AcademySoftwareFoundation/OpenImageIO/commit/9cda48b150294c7f024e680a6c9b0402e50f4816
Exploit, Third Party Advisory, Mitre
- github.com/AcademySoftwareFoundation/OpenImageIO/pull/5268
Exploit, Third Party Advisory, Mitre
- github.com/AcademySoftwareFoundation/OpenImageIO/releases/tag/v3.0.21.0
Exploit, Third Party Advisory, Mitre
- github.com/AcademySoftwareFoundation/OpenImageIO/releases/tag/v3.1.16.0
Exploit, Third Party Advisory, Mitre
- github.com/AcademySoftwareFoundation/OpenImageIO/security/advisories/GHSA-w6wc-gcf4-5pj2
Exploit, Third Party Advisory, Mitre
Elsewhere on this site
- AcademySoftwareFoundationevery CVE for this vendor
- Memory Corruptionsame class
- CWE-787other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-63419 is OpenImageIO: IFF ZBUFFER tile read writes past caller tile buffer, a high vulnerability affecting OpenImageIO from AcademySoftwareFoundation. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-63419. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-63419. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.8 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.