EUVD-2026-100597
GHSA-85v7-xg2x-pvvr
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious 3D file
-
DeliveryDeliver to victim via email or share
-
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 the victim to open a specially crafted file in Adobe Substance 3D Stager (version 3.1.8 or earlier); the malformed file triggers an out-of-bounds read during parsing. There is no network-remote trigger and no privilege prerequisite (PR:N), but mandatory user interaction (UI:R) is the primary limiting factor - the attacker must deliver the file and convince a legitimate Stager user to open it, and the resulting code runs only with that user's privileges (S:U, current-user context), not elevated. Not exploitable against a default install unless a user actively loads attacker-supplied content. |
| Impact | This is a genuine but not emergency-grade priority. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8 HIGH) is the dominant signal, and it is internally consistent with the description: AV:L (local) plus UI:R correctly reflects that exploitation is not remote-triggerable but instead requires a victim to open a malicious file on their own machine, yielding high confidentiality, integrity, and availability impact via code execution in the current user's context. The attack vector does NOT indicate network-reachable, unauthenticated mass exploitation; it is a user-interaction-gated client-side file-parsing bug, which materially lowers real-world risk relative to the 7.8 number. Key corroborating signals are MISSING: no EPSS score was provided, there is no CISA KEV listing in the input (no active exploitation), and no POC/exploit-code availability was indicated. No signals conflict with each other, but the absence of EPSS/KEV/POC means exploitation likelihood cannot be quantified. Net: treat as a routine-to-prompt patch item for environments running Substance 3D Stager, not a drop-everything incident. |
| Exploit ScenarioDerived | An attacker crafts a malicious 3D asset or project file and delivers it via email, a shared project, or a download, then socially engineers a Substance 3D Stager user into opening it. When Stager parses the crafted file, an out-of-bounds read past an allocated memory structure is triggered, which the attacker leverages to execute code in the context of the current user. No public exploit identified at time of analysis; exploitation requires the victim to open the file (AV:L/UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
An out-of-bounds read when parsing a crafted file in Adobe Substance 3D Stager 3.1.8 and earlier can be leveraged to execute code in the context of the current user, though exploitation is constrained by mandatory user interaction - a victim must open a maliciously crafted file. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), meaning it is triggered locally through file loading rather than over the network, requires no attacker-held privileges, and yields only the privileges of the user who opens the document. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV), so this is a genuine but not emergency-grade priority requiring timely patching rather than urgent incident response.
RemediationAI
The primary fix is to upgrade Substance 3D Stager past the affected 3.1.8 release to the patched version published in Adobe security bulletin APSB26-170 (https://www.adobe.com/trust/security/products/substance3d-stager/apsb26-170.html); the advisory is the authoritative source for the exact fixed build, so confirm the version in the bulletin or via the Creative Cloud updater rather than assuming. Until the upgrade is deployed, the most effective compensating control is to treat Stager project and asset files as untrusted input: block or quarantine 3D asset attachments at email and web gateways, and instruct users not to open files from unverified sources - the trade-off is reduced workflow flexibility for legitimate third-party assets. Because the vector is AV:L/UI:R with S:U, exploitation requires no privileges and no network exposure, so restricting who can run Stager and running it under a low-privilege, non-administrative account limits the blast radius of any successful code execution at the cost of some user convenience. Standard OS exploit mitigations (ASLR, DEP, CFG, and, on Windows, Arbitrary Code Guard / Code Integrity Guard where compatible) raise the difficulty of turning the out-of-bounds read into reliable code execution, but they are hardening measures, not fixes and may not be tolerated by 3D rendering workloads that rely on JIT or plug-in loading. There is no network-facing service to disable or port to block for this issue, so patching plus file-origin hygiene is the complete mitigation set.
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
The vulnerability is an out-of-bounds read (CWE-125) in Substance 3D Stager's file-parsing code path. When a malformed asset is loaded, the parser trusts length or offset fields in the file structure and reads beyond the end of the allocated buffer, producing an out-of-bounds access on memory that may belong to adjacent heap or stack structures. Because the affected code runs inside the Stager process, a successful exploit achieves arbitrary code execution in that process's security context - the current user - rather than requiring elevation. The CVSS vector confirms the root characteristics: AV:L (the trigger is local file open, not a network service), PR:N (no privileges needed by the attacker), UI:R (a legitimate user must open the file), and S:U (no sandbox or privilege boundary is crossed). The same parsing weakness also implies an information-disclosure angle, since out-of-bounds reads can leak memory contents in addition to corrupting control flow. Adobe's advisory assigns EUVD-2026-100597 and attributes the report to Adobe's PSIRT (psirt@adobe.com), classifying it alongside buffer-overflow/information-disclosure tags.
Know when the next one hits your stack
- 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-parsing bug needing no privileges but requiring the victim to open a malicious file (AV:L/PR:N/UI:R); code execution as current user yields C:H/I:H/A:H with unchanged scope.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
Substance3D - Stager is 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, the 3D scene composition tool used by our design and content teams, contains a memory-handling flaw in versions 3.1.8 and earlier that allows a maliciously crafted project file to run code on the workstation of whoever opens it. Because the attack requires a user to open a file rather than a network connection, the practical exposure sits with individual creatives and their endpoints - any assets received from external partners, contractors, or untrusted sources are a plausible delivery path. There is no vendor patch yet, so leadership should treat this as a manageable but time-bound risk requiring disciplined interim controls until Adobe ships a fix.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce a trusted-source-only policy for Stager project files and block or quarantine files received from external parties pending manual review; run file submissions through sandboxing or content-disassembly analysis before opening; ensure Adobe Substance 3D Stager runs under standard user privileges rather than administrator rights; enable endpoint detection and response monitoring for anomalous process creation originating from Stager; restrict the application to users who genuinely require it; and monitor Adobe security advisories to deploy the vendor fix immediately upon release.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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.
Exploit-DB