Substance3D - Stager versions 3.1.6 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.
Security readout for executives and security teams
Plain-English summary
A malicious file opened in Adobe Substance 3D Stager could exploit a memory-reading flaw and run attacker-controlled code with the victim’s user permissions. The victim must open the file, so organizations exchanging untrusted 3D assets face the greatest risk.
Executive priority
Treat as a high-priority workstation vulnerability, especially for design teams handling external assets. Remediate promptly through normal emergency-patching governance; immediate organization-wide crisis action is not supported because exploitation requires user interaction and no active exploitation evidence is provided.
Technical view
CVE-2026-21344 is a CWE-125 out-of-bounds read in Substance 3D Stager’s crafted-file parsing. It can read beyond an allocated memory structure and potentially achieve code execution as the current user. CVSS 3.1 is 7.8: local attack vector, low complexity, no privileges, and required user interaction.
Likely exposure
Exposure is likely where Substance 3D Stager 3.1.6 or earlier is installed and users open externally supplied or otherwise untrusted files. The bundle’s structured affected-version data is ambiguous, so validate exact affected and corrected versions against Adobe’s advisory.
Exploitation context
Exploitation requires convincing a user to open a malicious file. The supplied bundle reports no CISA KEV listing and provides no evidence of active exploitation. A successful attack could compromise confidentiality, integrity, and availability within the current user’s security context.
Researcher notes
The source bundle states 3.1.6 and earlier are affected, while its structured version entry contains “0” and “3.1.7” without range semantics. Do not interpret 3.1.7’s status solely from that entry. Confirm boundaries and remediation directly in APSB26-20. No exploit mechanics or indicators are included.
Mitigation direction
Review Adobe advisory APSB26-20 and apply the vendor-recommended corrected release.
Prioritize systems whose users receive or download untrusted 3D assets.
Restrict or quarantine untrusted Stager-compatible files until systems are remediated.
Use least-privileged user accounts to limit consequences of successful code execution.
Validation and detection
Inventory Substance 3D Stager installations and record their exact versions.
Compare installed versions with Adobe advisory APSB26-20’s affected and corrected versions.
Confirm remediated endpoints no longer run versions identified as vulnerable by Adobe.
Review file-delivery telemetry for untrusted assets opened with Stager on affected systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.