Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious Substance 3D Painter file
-
DeliveryDeliver via phishing or asset-sharing platform
-
ExploitVictim opens file in Substance 3D Painter
-
ExecutionOOB write corrupts application memory
-
PersistRedirect control flow to attacker shellcode
-
ImpactExecute arbitrary code as current user
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a victim user to manually open a malicious file using Adobe Substance 3D Painter (UI:R). The attack vector is local (AV:L): the crafted file must be present on the victim's filesystem or accessible via a mounted share and opened through the application. No authentication or elevated privileges are required of the attacker (PR:N) - only the ability to deliver the malicious file and socially engineer the victim into opening it. Exploitation is limited to the current user's privilege context (S:U), meaning post-exploitation impact is bounded to that user's accessible files and sessions. Non-default configurations are not required; any standard installation of Substance 3D Painter that can open project or asset files is vulnerable. The primary limiting factor is the mandatory user interaction step - automated or unauthenticated remote exploitation without file-open interaction is not possible given the AV:L/UI:R vector. |
| Impact | The CVSS 7.8 High score with AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H accurately represents the risk profile: full system impact (C:H/I:H/A:H) on the vulnerable system but constrained by the requirement for local user interaction (UI:R). No EPSS data was supplied in the intelligence package, preventing a probabilistic exploitation comparison. The absence of a CISA KEV listing and no noted POC means exploitation status is currently 'no public exploit identified at time of analysis' - however, file-format RCE vulnerabilities in creative software are historically weaponized through targeted phishing against designers and studio personnel, making the practical risk higher than a raw EPSS percentile might reflect. The low attack complexity (AC:L) once a victim opens the file suggests that exploit development - if pursued - would not require unusual technical barriers. The unchanged scope (S:U) limits lateral blast radius to the current user context, which is a mitigating factor in enterprise environments with privilege separation. Overall, this is a credible and high-severity threat in targeted scenarios against its specific user population, but not a broadly automated exploitation risk in its current state. |
| Exploit ScenarioDerived | An attacker crafts a maliciously structured Substance 3D Painter project or asset file designed to trigger an out-of-bounds write in the application's file parser. The file is delivered to a target - likely a 3D artist, game developer, or VFX professional - via email, a compromised asset-sharing platform, or a poisoned online asset library. Upon opening the file, the OOB write corrupts memory in a way that redirects execution, allowing the attacker to run arbitrary code silently under the victim's user account with no further interaction required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Out-of-bounds write in Adobe Substance 3D Painter enables arbitrary code execution under the privileges of the current user when a victim opens a specially crafted malicious file. The flaw (CWE-787) resides in file-parsing logic and delivers full confidentiality, integrity, and availability compromise of the affected system. No public exploit code or CISA KEV listing is identified at time of analysis, but the file-delivery vector makes this a credible threat for spear-phishing campaigns targeting creative and game-development professionals.
RemediationAI
Apply the vendor-released patch documented in Adobe Security Bulletin APSB26-129 at https://helpx.adobe.com/security/products/substance3d_painter/apsb26-129.html - the exact fixed version must be retrieved from that advisory, as no specific patched version number was included in the available intelligence data. Until the patch is applied, the most effective compensating control is to prohibit opening Substance 3D Painter project or asset files received from untrusted external sources such as email attachments, file-sharing links, or third-party asset marketplaces; this directly neutralises the UI:R attack vector. Organisations may also consider sandboxing Substance 3D Painter via OS-level application isolation (e.g., Windows Sandbox, macOS App Sandbox if supported) to limit post-exploitation blast radius to the current user context. Note that sandboxing trade-offs include potential restrictions on network-connected asset libraries and plugin ecosystems.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Adobe Substance 3D Painter is a PBR (physically-based rendering) texturing and painting application widely used in game development and VFX pipelines. CWE-787 (Out-of-Bounds Write) describes a condition in which a program writes data beyond the bounds of an allocated memory buffer, typically corrupting adjacent memory. In the context of a creative application such as Substance 3D Painter, this class of flaw commonly manifests in file-format parsers handling complex proprietary or third-party asset formats (e.g., mesh, texture, or project files). The CPE string cpe:2.3:a:adobe:adobe_substance_3d_painter:*:*:*:*:*:*:*:* indicates all tracked versions are affected, with no version upper bound specified. The CVSS vector AV:L reflects the local execution model - the malicious artifact must be opened by the target user - while the CWE tags (Memory Corruption, Buffer Overflow) indicate this is a classic heap or stack corruption primitive that can be leveraged for control-flow hijacking.
Know when Adobe Substance 3D Painter 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:H/I:H/A:H
File must be opened locally (AV:L), no privileges needed to deliver it (PR:N), user must open it (UI:R), and full impact is confined to the current user's system (S:U/C:H/I:H/A:H).
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
Substance3D - Painter is affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Executive ViewAI
Adobe Substance 3D Painter contains a critical out-of-bounds write vulnerability (CVE-2026-75749, CVSS 7.8) that enables full system compromise when users open malicious files, creating significant risk for creative and game-development teams. With no patch currently available and demonstrated feasibility for targeted spear-phishing delivery, this vulnerability represents an immediate and material threat to organizations relying on this software for business-critical content creation.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable Adobe Substance 3D Painter on non-critical systems; (2) Implement strict external file restrictions and advanced file-scanning; (3) Apply network segmentation to isolate affected workstations; (4) Deploy EDR with process-behavior monitoring for unauthorized code execution; (5) Restrict file access to authenticated internal delivery mechanisms only; (6) Conduct controlled file operations in air-gapped sandbox environments.
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.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Adobe Substance 3D Painter
View allHeap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution under the logged-in user's con
Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution within the context of the curr
Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution in the context of the current
Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution at the privilege level of the
Untrusted Search Path exploitation in Adobe Substance 3D Painter allows an attacker to achieve arbitrary code execution
Out-of-bounds write in Adobe Substance 3D Painter enables arbitrary code execution within the current user's security co
Out-of-bounds read in Adobe Substance 3D Painter exposes sensitive process memory when a victim opens a specially crafte
EUVD-2026-65682
GHSA-2q2p-5377-jqwp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB