Substance3D - Stager versions 3.1.7 and earlier are affected by an out-of-bounds write 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.
Security readout for executives and security teams
Plain-English summary
A malicious Substance 3D Stager file can corrupt memory and potentially run attacker-controlled code when opened. Successful exploitation could expose or alter data and disrupt the application under the victim’s user privileges. The victim must actively open the crafted file.
Executive priority
Prioritize remediation in the normal high-severity cycle, accelerating systems used to process third-party content. The user-interaction requirement reduces immediate exposure, but successful exploitation can compromise all data and capabilities available to the affected user.
Technical view
CVE-2026-27273 is a local, user-interaction-dependent out-of-bounds write in Adobe Substance 3D Stager. The supplied description identifies versions 3.1.7 and earlier as affected. It carries CVSS 3.1 score 7.8 and may enable arbitrary code execution with high confidentiality, integrity, and availability impact in the current user context.
Likely exposure
Exposure is most likely on endpoints running Substance 3D Stager 3.1.7 or earlier, particularly where users receive project files from external or untrusted sources. The supplied structured version data is ambiguous, so organizations should reconcile installed versions against Adobe APSB26-29.
Exploitation context
Exploitation requires a victim to open a malicious file; no prior application privileges are required. The source bundle marks the CVE as absent from KEV and provides no evidence of active exploitation. Treat unsolicited or externally sourced Stager files as the primary delivery risk.
Researcher notes
The weakness is CWE-787 with vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. The narrative says 3.1.7 and earlier are affected, while the structured affected entry contains “0” and “3.1.8” with defaultStatus “unaffected.” Confirm precise range semantics and fixed versions through Adobe’s advisory before final scoping.
Mitigation direction
Review and apply Adobe’s remediation guidance in APSB26-29.
Prioritize endpoints running Substance 3D Stager 3.1.7 or earlier.
Until remediated, prevent users from opening untrusted or unsolicited Stager files.
Use endpoint protections to inspect files and detect abnormal Stager child-process behavior.
Validation and detection
Inventory Substance 3D Stager installations and record exact versions.
Confirm no identified installation remains on version 3.1.7 or earlier after remediation.
Verify the deployed update matches Adobe APSB26-29 guidance.
Review endpoint telemetry for suspicious activity following Stager file opens.
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-787: 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.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.