Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious Substance 3D file to victim
-
ExploitVictim opens file in Designer
-
ExecutionParser triggers stack-based buffer overflow
-
ImpactApplication crashes (denial-of-service)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
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 | Exploitation requires a victim running Adobe Substance 3D Designer (version ≤16.0.4) to open an attacker-supplied malicious file within the application; there is no remote, network, or unauthenticated service-facing exploitation path. Limiting factors: the attack vector is local (AV:L), mandatory user interaction is required (UI:R - the victim must actively open the crafted file), and impact is confined to availability (application crash/DoS) with no confidentiality or integrity effect. This means successful exploitation depends entirely on social engineering to induce file opening, and the payoff is limited to disrupting the artist's session rather than compromising data or the host. |
| Impact | This is a genuine but comparatively low-priority issue. The CVSS vector (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, base 5.5 MEDIUM) describes a local, file-based attack with no confidentiality or integrity impact - only availability (an application crash). The UI:R requirement (victim must open a malicious file) and local attack vector substantially cap real-world risk, as exploitation cannot be performed remotely or automatically against exposed services. No EPSS score was provided in the input, so exploitation probability cannot be quantified. The CVE is NOT in CISA KEV and no public exploit code is referenced, so there is no public exploit identified at time of analysis. The only consequence is denial-of-service (crash); there is no indication of code execution despite the stack-based buffer overflow (CWE-121) root cause - Adobe scoped impact to A:H / C:N / I:N, meaning memory-safety exploitation for RCE was either not demonstrated or not achievable. Net: a legitimate vulnerability worth patching in the normal cycle, not an emergency. Note the signals are internally consistent (local vector + user interaction + availability-only), so there is no conflicting data to flag here, though the absence of EPSS limits probabilistic risk ranking. |
| Exploit ScenarioDerived | An attacker crafts a malicious Substance 3D Designer project or material/asset file and delivers it to a 3D artist via email, a shared asset library, or a download, relying on social engineering. When the victim opens the file in a vulnerable version (≤16.0.4), a stack-based buffer overflow is triggered and the application crashes, interrupting the user's work. No public exploit code is identified at time of analysis, and the flaw yields only denial-of-service, not code execution. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
A stack-based buffer overflow in Adobe Substance 3D Designer (versions 16.0.4 and earlier) allows an attacker to crash the application by supplying a crafted file that the victim opens, producing a denial-of-service condition for the active session. The attack is local (AV:L) and depends entirely on social engineering, since the victim must actively open the malicious asset (UI:R); no privileges are required (PR:N) and the impact is limited to availability with no confidentiality or integrity loss. Exploitation yields only an application crash rather than host compromise, and no public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
Apply the fix described in Adobe's security bulletin APSB26-169 (https://www.adobe.com/trust/security/products/substance3d-designer/apsb26-169.html) - patch availability is confirmed by the vendor advisory, though the provided data does not specify the exact fixed version number, so consult the bulletin for the precise build to install (any release above the affected 16.0.4 line). Because the vulnerability is only reachable when a user opens a malicious file, the primary compensating control is to treat untrusted Substance project files as hazardous: validate or sandbox incoming .sbs/.sbsar-style assets before opening them in a production Designer session, and avoid opening assets from unknown or unverified sources. Where immediate patching is not possible, restrict Designer file-opening to vetted content libraries and consider running the application in a low-privilege, isolated environment so that a crash cannot affect other work; note that isolation adds friction to the artist workflow and does not remove the crash itself. There is no server-side or network control that mitigates this issue because the attack vector is purely local with mandatory user interaction.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic stack-based buffer overflow (CWE-121) in Adobe Substance 3D Designer, a procedural material and texture authoring tool used by 3D artists. Parsing of an attacker-controlled file - most plausibly a Substance package/procedural asset - copies data into a fixed-size stack buffer without adequate bounds validation, corrupting adjacent stack memory. With the assessed CVSS:3.1 vector AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, the corrupted state is not leveraged for code execution in the assessed impact; the observable outcome is process termination (application denial-of-service). The CWE class is dangerous because stack overflows can theoretically be escalated to arbitrary code execution when stack protections are bypassable, but the authoritative assessment here confines impact to availability only. Affected builds are Substance 3D Designer 16.0.4 and prior; the issue is tracked by Adobe PSIRT and mirrored in ENISA EUVD as EUVD-2026-100701.
Know when Substance 3d Designer 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
Exploitation needs a locally opened malicious file (AV:L, UI:R) with no prior privilege (PR:N); impact is an application crash only, so C:N/I:N/A:H.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
Substance3D - Designer is affected by a Stack-based Buffer Overflow vulnerability that could result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
More in Substance 3d Designer
View allOut-of-bounds write in Adobe Substance 3D Designer 16.0.4 and earlier allows arbitrary code execution in the context of
Substance3D - Designer versions 14.0.2 and earlier are affected by an out-of-bounds write vulnerability that could resul
Arbitrary code execution in Substance 3D Designer 15.0.3 and earlier results from an out-of-bounds write vulnerability t
Substance3D - Designer versions 14.1 and earlier are affected by an out-of-bounds write vulnerability that could result
Substance3D - Designer versions 14.1 and earlier are affected by an out-of-bounds write vulnerability that could result
Substance3D - Designer versions 14.1 and earlier are affected by an out-of-bounds write vulnerability that could result
Arbitrary code execution in Substance 3D Designer 15.1.0 and earlier via an out-of-bounds write vulnerability that trigg
Arbitrary code execution in Substance 3D Designer 15.1.0 and earlier through an out-of-bounds write vulnerability that r
Substance3D - Designer versions 13.1.2 and earlier are affected by an out-of-bounds write vulnerability that could resul
Substance3D - Designer versions 13.1.0 and earlier are affected by an out-of-bounds read vulnerability when parsing a cr
Adobe Substance 3D Designer versions 13.0.0 (and earlier) and 13.1.0 (and earlier) are affected by an out-of-bounds writ
Adobe Substance 3D Designer version 12.4.1 (and earlier) is affected by an Access of Uninitialized Pointer vulnerability
EUVD-2026-100701
GHSA-vh29-8wfc-qc73
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB