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
Adobe Substance 3D Stager 3.1.7 and earlier can be compromised when a user opens a malicious file. Successful exploitation could let attacker-controlled code run with that user’s permissions, potentially exposing data, changing files, or disrupting the workstation.
Executive priority
Treat this as a high-priority endpoint remediation, especially for design teams exchanging external files. Prioritize exposed creative workstations and managed update enforcement. Required user interaction and the absence of supplied active-exploitation evidence reduce emergency pressure, but the potential business impact remains substantial.
Technical view
CVE-2026-27275 is an out-of-bounds write (CWE-787) in Substance 3D Stager. It may enable arbitrary code execution as the current user. CVSS 3.1 scores it 7.8: local attack vector, low complexity, no privileges required, and required user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is concentrated on endpoints running Substance 3D Stager 3.1.7 or earlier, particularly where users receive or open files from external or untrusted sources. The supplied evidence does not indicate a remotely exploitable service or exposure without a user opening a malicious file.
Exploitation context
Exploitation requires convincing a user to open a malicious file. The supplied bundle says this CVE is not in CISA KEV and provides no evidence of active exploitation. That lowers immediate urgency relative to known-exploited vulnerabilities, but successful exploitation could still produce complete workstation-level impact within the user’s permissions.
Researcher notes
The source description explicitly identifies 3.1.7 and earlier as affected. The structured affected-version entry also contains “0” and “3.1.8,” but its range semantics are not explained in the bundle. Confirm exact fixed-version boundaries in Adobe APSB26-29. No exploit mechanics, indicators of compromise, or confirmed exploitation campaigns are provided.
Mitigation direction
Inventory Substance 3D Stager installations and identify versions 3.1.7 or earlier.
Follow Adobe APSB26-29 and move affected installations to a vendor-confirmed non-affected release.
Until remediated, prevent affected users from opening untrusted or externally supplied Stager files.
Use endpoint protections and least-privilege accounts to limit consequences of user-context code execution.
Validation and detection
Confirm installed Stager versions through software inventory and endpoint management records.
Verify remediated systems no longer run version 3.1.7 or earlier.
Review Adobe APSB26-29 to confirm the applicable release and platform-specific instructions.
Review endpoint telemetry for unusual Stager behavior associated with recently opened external files.
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.