Substance3D - Designer versions 15.0.3 and earlier are affected by an Out-of-bounds Read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to disclose sensitive information stored in memory. 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 Designer 15.0.3 or earlier could expose sensitive information from application memory. The victim must deliberately open the file. The supplied evidence does not indicate code execution, data modification, service disruption, or active exploitation.
Executive priority
Treat as a normal, time-bounded workstation remediation rather than an emergency. Prioritize creative teams receiving files from customers, contractors, or public sources because successful exploitation could expose sensitive memory contents.
Technical view
CVE-2026-21308 is a CWE-125 out-of-bounds read with CVSS 3.1 score 5.5. It is locally triggered without privileges but requires user interaction. Successful exploitation may disclose memory contents; integrity and availability impacts are not identified.
Likely exposure
Exposure is most likely on workstations running Substance 3D Designer 15.0.3 or earlier whose users open untrusted or externally supplied project files. Systems without the product, or where suspicious files cannot reach users, have lower exposure.
Exploitation context
A threat actor must persuade a user to open a malicious file locally. The supplied bundle marks the CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. That does not prove exploitation is impossible.
Researcher notes
The structured affected-version field includes “0” and “15.1.0,” while the description explicitly states 15.0.3 and earlier. The bundle does not explain that discrepancy or name a fixed release. Use Adobe's advisory as the authority before finalizing detection logic or remediation compliance.
Mitigation direction
Inventory Substance 3D Designer installations and prioritize versions 15.0.3 or earlier.
Review Adobe's advisory and apply its vendor-recommended update or mitigation.
Restrict or quarantine unsolicited Substance 3D files until affected systems are remediated.
Remind users not to open unexpected design files from untrusted sources.
Validation and detection
Confirm the installed Substance 3D Designer version on each relevant workstation.
Compare discovered versions with Adobe's current advisory and documented affected range.
Verify the vendor-recommended remediation is installed successfully.
Review file-delivery controls for untrusted Substance 3D content.
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.
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.