Substance 3D Stager
CVE-2025-61806
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted 3D file to victim
-
ExploitVictim opens file in Stager
-
ExecutionTrigger out-of-bounds read in parser
-
ImpactExecute code as current user
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 that a victim running Adobe Substance 3D Stager (version 3.1.4 or earlier) locally open an attacker-crafted malicious file; the out-of-bounds read is triggered specifically during the parsing of that crafted file. Key limiting factors: the attack is local (AV:L) and cannot be triggered remotely without user action - it depends entirely on social engineering to deliver and have the victim open the file (UI:R), and resulting code execution is confined to the privileges of the current user (S:U), not SYSTEM/root. There is no network-facing or unauthenticated-service exposure. |
| Impact | This is a moderate-priority, not a drop-everything, issue. The CVSS 3.1 base score of 7.8 is driven entirely by local attack vector (AV:L) with low complexity and no privileges, but gated by required user interaction (UI:R): a victim must open an attacker-supplied malicious file. The claimed impact (C:H/I:H/A:H) reflects Adobe's position that the out-of-bounds read (CWE-125) can be leveraged to execute code in the current user's context, though the described primitive is fundamentally a memory read-past-end, so reliable code execution is plausible but not guaranteed and would typically require additional exploitation effort. Exploitation signals are weak: EPSS is only 0.21% (10th percentile), there is no CISA KEV listing, and no public exploit code was identified - the vulnerability is not under known active exploitation. The signals are internally consistent (local, user-interaction-dependent file-parsing bug with low mass-exploitation probability), with no major conflicts; the only tension worth noting is that a pure out-of-bounds READ (CWE-125) maps less naturally to full I:H/A:H code-execution impact than the vendor rating implies - verify the exact exploitation primitive with Adobe if precise impact matters. Overall this behaves like a typical client-side file-parsing flaw: real but requiring social engineering, best handled via normal patch cycles rather than emergency response. |
| Exploit ScenarioDerived | An attacker crafts a malicious 3D scene or asset file and delivers it to a victim via email, a shared project, or a download, relying on social engineering to get them to open it in Substance 3D Stager. When Stager parses the crafted file, an out-of-bounds read occurs in the parsing logic, which the attacker leverages to execute code in the context of the current user. No public proof-of-concept or exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Out-of-bounds read in Adobe Substance 3D Stager 3.1.4 and earlier is triggered while parsing a crafted file, letting an attacker read past the end of an allocated memory structure and potentially execute code in the context of the current user. The issue is local (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8) and depends on the victim opening a malicious file, so delivery requires user interaction and social engineering rather than remote, unauthenticated exposure. EPSS is 0.21% (10th percentile), there is no CISA KEV entry, and no public exploit identified at time of analysis, making this a moderate-priority, not a drop-everything, issue.
RemediationAI
Apply the vendor update for Adobe Substance 3D Stager referenced in Adobe security advisory APSB25-104 (https://helpx.adobe.com/security/products/substance3d_stager/apsb25-104.html); patch availability is confirmed by the vendor advisory, so upgrade to the latest fixed release listed there rather than relying on a specific version number not provided in the source data. Because exploitation requires the victim to open a malicious file, prioritize controls that reduce exposure to untrusted content: block or quarantine Stager project and asset files from unknown or unsolicited sources, restrict file-association exceptions so Stager files do not auto-launch, and run Stager under a least-privilege user account so any code execution stays confined to that user's context. Additional compensating measures include using the OS mail/web gateway to strip or sandbox attachments that reference Stager file types, and monitoring for unusual child processes spawned by Stager; these reduce risk but do not eliminate it, since the underlying out-of-bounds read remains until the patch is applied. There is no evidence that network-level blocking alone is sufficient, because the attack vector is local and depends on user interaction.
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 an out-of-bounds read (CWE-125) in the file-parsing path of Adobe Substance 3D Stager, a 3D scene staging and rendering application used by designers and artists. When the application parses a specially crafted file, it reads beyond the end of an allocated memory structure; this memory-safety class of bug is primarily an information-disclosure primitive, but under the right memory layout and data-flow conditions it can be chained toward code execution, which is why Adobe and NVD score it with high confidentiality, integrity, and availability impact (C:H/I:H/A:H). The CVSS vector AV:L/UI:R/PR:N/S:U confirms the attacker has no privileges on the target and the exploit is local-only, requiring a user to open the crafted file; successful code execution is confined to the current user's privileges rather than SYSTEM or root. The only affected CPE is cpe:2.3:a:adobe:substance_3d_stager:*:*:*:*:*:*:*:*, applying to Stager 3.1.4 and earlier across supported desktop platforms. Tags for the CVE also reference Buffer Overflow and Information Disclosure, consistent with memory-corruption primitives associated with unsafe parsing of input files.
Know when Substance 3d Stager 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
Local file-open attack (AV:L, UI:R) needing no prior privileges (PR:N); vendor-asserted code execution in user context justifies C/I/A:H with unchanged scope.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
Substance3D - Stager versions 3.1.4 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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 Stager 3.1.4 and earlier contains a high-severity local file-parsing vulnerability that could allow code execution with the victim's permissions if a crafted file is opened. The risk is concentrated among creative and design teams handling untrusted assets, where a compromise could expose project data and the workstation, though exploitation requires user interaction and there is no public exploit identified at time of analysis. Leadership should treat this as a targeted workstation risk and prioritize safe file-handling controls while monitoring for a vendor fix.
No vendor patch identified; restrict opening untrusted Substance 3D Stager project files, enforce least privilege, application allowlisting, EDR monitoring, sandbox isolation, email/web filtering, and disable preview or thumbnail handlers for untrusted files where feasible.
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
More in Substance 3d Stager
View allUse-after-free memory corruption in Adobe Substance 3D Stager 3.1.4 and earlier allows an attacker to execute arbitrary
Arbitrary code execution in Adobe Substance 3D Stager 3.1.4 and earlier is possible when a victim opens a specially craf
An out-of-bounds read in Adobe Substance 3D Stager 3.1.4 and earlier allows a crafted 3D asset file to cause the parser
Arbitrary code execution in the context of the current user is possible in Adobe Substance 3D Stager 3.1.4 and earlier w
Substance3D - Stager versions 3.1.1 and earlier are affected by a Use After Free vulnerability that could result in arbi
Substance3D - Stager versions 3.1.1 and earlier are affected by a Use After Free vulnerability that could result in arbi
Arbitrary code execution in Substance 3D Stager 3.1.5 and earlier stems from a use-after-free vulnerability that execute
Arbitrary code execution in Substance 3D Stager 3.1.6 and earlier via an out-of-bounds write vulnerability allows local
Arbitrary code execution in Substance 3D Stager 3.1.7 and earlier through a use-after-free memory vulnerability that tri
Arbitrary code execution in Substance 3D Stager 3.1.7 and earlier stems from a use-after-free vulnerability that execute
Code execution in Substance 3D Stager 3.1.6 and earlier through a crafted file that triggers an out-of-bounds memory rea
Substance 3D Stager 3.1.6 and earlier contains an out-of-bounds read vulnerability in file parsing that allows arbitrary
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB