Substance 3D Stager
CVE-2025-61807
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious crafted file to victim
-
DeliveryVictim opens file in Substance 3D Stager
-
ExploitTrigger integer overflow in file parser
-
ExecutionCorrupt memory and hijack control flow
-
ImpactExecute arbitrary code as current user
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 | Exploitation requires that a victim user manually open an attacker-supplied malicious file in Adobe Substance 3D Stager version 3.1.4 or earlier; it cannot be triggered remotely or without user action. The CVSS vector (AV:L/UI:R) confirms a local attack vector with mandatory user interaction, which is the primary limiting factor - there is no network-facing service, no autonomous or wormable path, and code execution is confined to the privileges of the current user (S:U, no privilege escalation). While PR:N means no prior authentication to the application is needed, the social-engineering step of inducing the victim to open a crafted file is the practical gating condition, and resulting access is bounded by that user's OS-level permissions. |
| Impact | Severity is driven by high technical impact (C:H/I:H/A:H) enabling arbitrary code execution, but all exploitation-likelihood signals point to low real-world urgency. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R) confirms this is a LOCAL, file-based attack requiring the victim to open a malicious file - not a remotely reachable network service - so the 7.8 'HIGH' base score overstates the autonomy of exploitation. EPSS reinforces this: 0.21% probability at only the 10th percentile indicates the model sees very low likelihood of exploitation in the next 30 days. The CVE is NOT on CISA KEV and no public exploit code was provided, so there is no public exploit identified at time of analysis. No SSVC decision data was supplied. Net assessment: this is a legitimate code-execution flaw that should be patched, but it is a client-side, user-interaction-gated issue in a specialized desktop tool rather than a mass-exploitation priority - closer to a 'high-CVSS, moderate-real-risk' bug. Signals are internally consistent (local vector + UI requirement + low EPSS all agree); no conflicts to flag beyond the usual caveat that base CVSS does not discount for the required user interaction. |
| Exploit ScenarioDerived | An attacker crafts a malicious 3D project or asset file that triggers the integer overflow (CWE-190) during parsing in Substance 3D Stager, then distributes it via email, a shared asset marketplace, or a collaboration channel. When a 3D artist opens the file in a vulnerable version (≤3.1.4), the overflow corrupts memory and leads to arbitrary code execution in the context of that user. No public exploit code has been identified at time of analysis, so exploitation would currently require independent development of a working payload. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Arbitrary code execution in Adobe Substance 3D Stager 3.1.4 and earlier is possible when a victim opens a specially crafted file, because an integer overflow or wraparound in the application's file handling leads to memory corruption that can be steered into code execution. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confirms the attack is local and demands mandatory user interaction: there is no network-facing service, no autonomous or wormable path, and any code that executes runs only with the privileges of the current user (no sandbox escape or privilege escalation). No public exploit code has been identified at time of analysis and the EPSS score is low at 0.21% (10th percentile), so while the technical impact is high once the file is opened, exploitation-likelihood signals point to low real-world urgency.
RemediationAI
Update Substance 3D Stager to the version identified in Adobe's security bulletin APSB25-104 (https://helpx.adobe.com/security/products/substance3d_stager/apsb25-104.html); the bulletin is the authoritative source for the exact fixed build, and the assessment here confirms the pre-fix exposure applies to 3.1.4 and earlier. Patch status per input data is: Patch available per vendor advisory. Because exploitation requires the user to open a malicious file, the most effective compensating controls are at the file-handling boundary: instruct users not to open Stager project, model, or material files received from untrusted or unexpected sources, and strip or quarantine those file types at the email gateway and web proxy (trade-off: this blocks legitimate collaboration workflows and can break automated asset pipelines that move scene files between artists). Where removable or network asset shares are used, restrict write access so untrusted parties cannot deposit crafted files into directories artists open routinely (trade-off: added friction for shared-production workflows). Running Stager in a low-privileged OS account limits the blast radius of any successful exploitation since code runs only at the current user's privilege level (trade-off: some rendering and asset-cache operations may need extra permissions). Application allow-listing and endpoint detection tuned to child-process creation by the Stager binary can help catch post-exploitation activity, but neither prevents the parsing overflow itself, so applying the vendor update remains the primary fix.
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 root cause class is CWE-190, Integer Overflow or Wraparound. In this class, arithmetic performed on attacker-influenced length, size, offset, or count values (for example, computing a buffer size or an array index from values embedded in a 3D asset, material, or scene file) is not checked for overflow. When the computed value wraps to a small or negative number, a subsequent allocation or bounds check uses the wrapped result, so data is written past the end of the intended buffer - a classic heap or stack memory-corruption primitive. In the context of Substance 3D Stager, a desktop 3D scene composition and staging tool that ingests multiple third-party model and material formats, this overflow occurs while parsing an attacker-supplied file. The CPE cpe:2.3:a:adobe:substance_3d_stager:*:*:*:*:*:*:*:* marks the whole product line before the fixed release as affected, and the Adobe security bulletin APSB25-104 is the authoritative vendor advisory. Because the CVSS vector carries AV:L and UI:R, the memory-corruption primitive is reachable only through the local file-open path rather than through any network or service interface, and successful exploitation yields code execution in the current user's context (S:U, scope unchanged).
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 app authentication (PR:N); successful memory-corruption RCE yields full user-context C/I/A impact within an unchanged scope.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
Substance3D - Stager versions 3.1.4 and earlier are affected by an Integer Overflow or Wraparound 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 Stager 3.1.4 and earlier contain a high-severity local code execution flaw that triggers when a user opens a malicious file. The exposure is limited to the privileges of the affected user and requires deliberate file interaction; no public exploit identified at time of analysis, so immediate exploitation likelihood appears low. Leadership should care because no vendor-released patch identified at time of analysis leaves user behavior and file-handling controls as the primary defenses for creative and design teams.
No vendor-released patch identified at time of analysis. Interim mitigations include blocking or quarantining untrusted Stager project files at email and web gateways, training users not to open unsolicited design files, applying least privilege to accounts running Adobe Substance 3D Stager, enabling EDR monitoring for unusual process behavior from Stager, and using application allowlisting or isolated environments for file opening. Monitor Adobe advisories for a patch and apply it immediately when released.
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
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
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
Out-of-bounds read in Adobe Substance 3D Stager 3.1.4 and earlier is triggered while parsing a crafted file, letting an
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