Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconCraft malicious CbYCrY image
-
DeliveryDeliver via email/share/upload
-
ExploitUser processes image
-
InstallTrigger integer overflow in ConvertCbYCrYToRGB()
-
C2Write out-of-bounds via negative offset
-
ExecuteCorrupt process memory
-
ImpactCrash application or execute code
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires user interaction (UI:R per CVSS vector) to process attacker-supplied CbYCrY format image files through applications using vulnerable OpenImageIO versions. Specifically targets the ConvertCbYCrYToRGB() color space conversion function, meaning exploitation occurs only when processing images that invoke this conversion pathway - not all image formats or workflows trigger the vulnerable code. No authentication required (PR:N) for network-based delivery scenarios where attackers can supply images to targets via email attachments, cloud storage shares, web uploads, or collaborative asset management systems. Limiting factors include: user must actively open or process the malicious image rather than passive exploitation, victim application must be compiled against or dynamically linked with OpenImageIO versions prior to patched releases (3.0.18.0/3.1.13.0), and memory corruption exploitability depends on target system memory layout and protection mechanisms (ASLR, DEP) which may reduce code execution likelihood while crash/DoS remains achievable. |
| Impact | CVSS 8.8 (High) reflects network-deliverable attack vector with low complexity, but requires user interaction (UI:R) - a realistic constraint in VFX workflows where artists routinely process third-party image assets. The vulnerability enables high-impact outcomes: confidentiality, integrity, and availability compromise through memory corruption. EPSS probability data unavailable for risk quantification. Not listed in CISA KEV, indicating no confirmed active exploitation campaigns. GitHub security advisory confirms vulnerability and patch availability, establishing high confidence in technical details. Real-world risk depends heavily on deployment context: automated image processing pipelines (render farms, asset ingestion systems) face higher exposure than interactive workstation use. Attack complexity is low (AC:L) once a malicious image is crafted, but weaponization requires understanding CbYCrY format specifics and integer overflow mechanics. Priority assessment: HIGH for internet-facing image processing services and shared rendering infrastructure; MEDIUM for isolated workstation environments with controlled asset sources. No POC publicly identified, reducing immediate weaponization risk, but image file format exploits have established weaponization history in targeted attacks against media/entertainment sectors. |
| Exploit ScenarioDerived | An attacker crafts a malicious CbYCrY-encoded image file with specific dimensional properties calculated to trigger signed integer overflow during pixel indexing. The victim, a VFX artist or automated asset pipeline, processes this image using an application built with vulnerable OpenImageIO versions. During ConvertCbYCrYToRGB() execution, the overflow produces large negative offsets that write pixel data outside allocated buffer boundaries, corrupting adjacent memory regions and crashing the application or potentially achieving code execution if memory layout is predictable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 14, 2026
Out-of-bounds write in OpenImageIO versions prior to 3.0.18.0 and 3.1.13.0 allows remote attackers to crash applications or potentially execute arbitrary code by delivering maliciously crafted CbYCrY image files. A signed integer overflow in the ConvertCbYCrYToRGB() pixel-loop calculation generates large negative pointer offsets, corrupting memory during image processing. EPSS data not available; no evidence of active exploitation (not in CISA KEV); exploitation requires user interaction to process attacker-supplied image files.
RemediationAI
Upgrade to OpenImageIO version 3.0.18.0 or later for 3.0.x deployments, or version 3.1.13.0 or later for 3.1.x deployments, as specified in GitHub security advisory GHSA-2jr5-q49v-3858 (https://github.com/AcademySoftwareFoundation/OpenImageIO/security/advisories/GHSA-2jr5-q49v-3858). Both versions contain patches that address the integer overflow in ConvertCbYCrYToRGB() by implementing safer index arithmetic. If immediate patching is not feasible, implement compensating controls: restrict image processing to trusted sources only, deploy input validation to reject CbYCrY format images or enforce strict dimensional limits before processing (note: may break legitimate workflows requiring this color space), and isolate image processing operations in sandboxed environments with limited privileges to contain potential exploitation impact (reduces consequences but does not prevent exploitation). For internet-facing services, deploy web application firewalls or content filters to block suspicious image uploads, though this provides limited protection against sophisticated format manipulation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
OpenImageIO is a widely-used C++ library in VFX and animation pipelines for reading, writing, and manipulating diverse image formats. The vulnerability resides in ConvertCbYCrYToRGB(), a color space conversion function that processes CbYCrY (chroma-luma) encoded image data. The pixel-loop uses expression 'i * 3' as an index with a signed 32-bit integer type. When processing malformed images with specific dimensional characteristics, this multiplication overflows the integer bounds (CWE-190: Integer Overflow or Wraparound), wrapping to large negative values. These negative values are then used as pointer offsets into the output buffer, resulting in out-of-bounds memory writes that bypass intended buffer boundaries. Affected products per CPE: OpenImageIO versions before 3.0.18.0 in the 3.0.x branch and before 3.1.13.0 in the 3.1.x branch, as published by the Academy Software Foundation.
Know when Openimageio gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
OpenImageIO 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, a signed 32-bit integer overflow in the pixel-loop index expression i * 3 inside ConvertCbYCrYToRGB() causes the function to compute a large negative pointer offset into the output buffer, producing an out-of-bounds write that crashes the process. This vulnerability is fixed in 3.0.18.0 and 3.1.13.0.
Executive ViewAI
OpenImageIO versions before 3.0.18.0 and 3.1.13.0 contain an out-of-bounds write vulnerability in image processing that could allow attackers to crash applications or execute arbitrary code when users process malicious CbYCrY image files. Organizations using OpenImageIO in content creation, media processing, or any image-handling workflows face application instability and potential compromise if users are tricked into opening untrusted images.
No vendor-released patch identified at time of analysis. Until patching is available: restrict image file processing to trusted sources only; implement application sandboxing or containerization to limit impact of code execution; use file validation tools to detect malformed CbYCrY files before processing; disable remote image loading features where not essential; monitor application logs for crashes or unexpected terminations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
More in Openimageio
View allBuffer Overflow vulnerability in OpenImageIO oiio v.2.4.12.0 allows a remote attacker to execute arbitrary code and caus
A code execution vulnerability exists in the DDS scanline parsing functionality of OpenImageIO Project OpenImageIO v2.4.
An out-of-bounds write vulnerability exists in the OpenImageIO::add_exif_item_to_spec functionality of OpenImageIO Proje
A heap based buffer overflow vulnerability exists in the PSD thumbnail resource parsing code of OpenImageIO 2.3.19.0. Ra
A heap based buffer overflow vulnerability exists in tile decoding code of TIFF image parser in OpenImageIO master-branc
A heap out-of-bounds write vulnerability exists in the way OpenImageIO v2.3.19.0 processes RLE encoded BMP images. Rated
A heap out of bounds read vulnerability exists in the handling of IPTC data while parsing TIFF images in OpenImageIO v2.
An issue in OpenImageIO oiio v.2.4.12.0 allows a remote attacker to execute arbitrary code and cause a denial of service
Multiple code execution vulnerabilities exist in the IFFOutput::close() functionality of OpenImageIO Project OpenImageIO
Multiple code execution vulnerabilities exist in the IFFOutput::close() functionality of OpenImageIO Project OpenImageIO
Multiple code execution vulnerabilities exist in the IFFOutput::close() functionality of OpenImageIO Project OpenImageIO
Multiple code execution vulnerabilities exist in the IFFOutput::close() functionality of OpenImageIO Project OpenImageIO
EUVD-2026-30413
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB