Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft PSD with invalid color_mode
-
DeliveryDeliver file to victim/pipeline with RawColor/RawData enabled
-
Exploitvalidate_header() raw path skips validation
-
Executionsetup() indexes color-mode tables out of bounds
-
PersistOut-of-bounds read and bogus allocation
-
ImpactProcess crash (denial of service)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the application to have enabled the non-default OpenImageIO options oiio:RawColor or psd:RawData, because validate_header() only bypasses normal color-mode validation on this raw path (m_WantRaw short-circuit). The attacker must supply a crafted PSD file with an out-of-range color_mode value, and a victim or automated pipeline must open/process it (UI:R, local vector AV:L). Exploitation is limited to local file processing, requires user interaction, and does not affect deployments that leave the raw color/data options disabled (the default); maximum impact is a crash, with no confidentiality or integrity effect. |
| Impact | This is a genuine but low-priority denial-of-service issue, not a high-impact vulnerability. The vendor CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H = 5.5 Medium) is internally consistent with the description: a local vector requiring a victim to open a crafted PSD file (UI:R), with pure availability impact (C:N/I:N/A:H) from a global out-of-bounds read and possible bogus allocation causing a crash. No EPSS score, no CISA KEV listing, and no public weaponized exploit are present in the input, so exploitation status is 'no public exploit identified at time of analysis' - though the fix PR ships a regression trigger file (bad_colormode.psd) that demonstrates the crash. The CWE-125 (out-of-bounds read) classification aligns with the described table-indexing over-read. A key limiting factor understated by raw CVSS: the flaw is only reachable when the non-default options oiio:RawColor or psd:RawData are enabled, because validate_header() short-circuits normal color-mode validation on the raw path. The 'Information Disclosure' tag conflicts with the vendor's C:N rating - impact is availability only, not disclosure. Overall: real, patched, but low real-world urgency given local-only vector, required user interaction, and non-default configuration gate. |
| Exploit ScenarioDerived | An attacker crafts a malformed PSD file with an out-of-range color_mode value and delivers it to a victim (or an automated pipeline) that processes images with OpenImageIO configured with oiio:RawColor or psd:RawData enabled. When the file is opened, PSDInput::setup() uses the attacker-controlled color_mode to index fixed color-mode tables past their bounds, causing an out-of-bounds read and possible invalid allocation that crashes the process. No standalone exploit is public, but the fix includes a proof-of-concept PSD test file demonstrating the trigger. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Denial of service in OpenImageIO's PSD reader allows a crafted PSD file carrying an invalid color_mode value to index beyond the fixed color-mode tables, producing a global out-of-bounds read and potentially a bogus allocation that crashes the reading process. The exposure is narrow: the raw path is only reachable when the non-default oiio:RawColor or psd:RawData option is explicitly enabled, and an attacker must get a target application or automated pipeline to open the malicious file (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, score 5.5, CWE-125), so impact is availability-only with no confidentiality or integrity effect. No public exploit has been identified at time of analysis, and vendor-released fixes exist in 3.0.21.0, 3.1.16.0, and 3.2.0.3-beta1.
RemediationAI
Vendor-released patch: upgrade to OpenImageIO 3.0.21.0, 3.1.16.0, or 3.2.0.3-beta1 (or later); the fix is carried in the tagged releases for each maintained branch and in commit 50481b0f90932a4675f65f3cc26407139cb9e20e from PR #5282, with details in advisory GHSA-3c8w-9xvm-r6gf. If immediate upgrading is not possible, the most effective compensating control is to ensure the raw PSD path is never enabled: leave the oiio:RawColor and psd:RawData configuration attributes at their defaults (disabled) and strip or ignore any caller-supplied iconfig that sets them, since validate_header() only skips color-mode validation when m_WantRaw is true - the trade-off is that downstream users lose raw access to duotone, Lab, multichannel, and other undocumented color-mode data. Additional hardening with its own costs includes rejecting or sandboxing untrusted PSD input at ingest (quarantine scanning, running image conversion in a restricted process with memory limits), and treating the crash as a containment boundary rather than relying on it, since the out-of-bounds read can also influence an allocation size and instability may vary by build. Patching remains the only control that removes the root cause, as there is no configuration option that validates color_mode while keeping the raw path active in affected versions.
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
The flaw lives in the PSD format reader at src/psd.imageio/psdinput.cpp, specifically the interaction between PSDInput::validate_header() and PSDInput::setup(). The PSD header carries a color_mode field (Bitmap, Grayscale, Indexed, RGB, CMYK, Multichannel, Duotone, Lab, and undocumented values), and the reader uses that field to select from fixed lookup tables such as mode_channel_count. Before the fix, validate_header() short-circuited with an early 'if (m_WantRaw) return true;' whenever raw access was requested via oiio:RawColor or psd:RawData, so no range check was performed on the attacker-controlled color_mode. PSDInput::setup() then fed the unvalidated value into table indexing, yielding a global out-of-bounds read (CWE-125) and potentially an attacker-influenced allocation. The upstream patch (PR #5282, commit 50481b0f90932a4675f65f3cc26407139cb9e20e) restructures validate_header() so color-mode validation runs before the raw short-circuit and adds an explicit default branch rejecting unknown modes, with a regression test (testsuite/psd-colormodes, bad_colormode.psd) confirming that an unrecognized mode such as 20 now fails header parsing instead of reaching setup().
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:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Local crafted-file vector with required victim interaction (AV:L/UI:R), no auth (PR:N), and crash-only impact (C:N/I:N/A:H); the raw-config gate is an app option, not attacker-controlled complexity.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.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.21.0, 3.1.16.0, and 3.2.0.3-beta1, A crafted psd with an invalid color_mode bypasses normal validation when oiio:rawcolor or psd:rawdata is enabled. psdinput::setup() then uses the attacker-controlled value to index fixed color-mode tables, causing a global out-of-bounds read and potentially a bogus allocation, resulting in denial of service. The affected implementation is identified by src/psd.imageio/psdinput.cpp, PSDInput::validate_header(), PSDInput::setup(), oiio:RawColor, psd:RawData, color_mode, and mode_channel_count, 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.
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.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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
Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
EUVD-2026-83125
NVD
CVE.org
EPSS
GitHub
Exploit-DB