Substance3D - Designer versions 15.1.0 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 could expose sensitive information held in the application's memory. The victim must deliberately open the file, limiting immediate risk, but exposed data could still be valuable to an attacker.
Executive priority
Prioritize normal-cycle remediation for affected creative workstations, accelerating systems that routinely handle external files or sensitive projects. The user-interaction requirement reduces urgency relative to remotely exploitable flaws, but possible memory disclosure warrants action.
Technical view
CVE-2026-21340 is a CWE-125 out-of-bounds read with CVSS 3.1 score 5.5. It requires local delivery and user interaction, needs no privileges, and may cause high-confidentiality impact without documented integrity or availability impact.
Likely exposure
Workstations running affected Substance 3D Designer versions are most exposed when users receive and open files from external or untrusted sources. The bundle contains conflicting affected-version information, so exact exposure requires confirmation against Adobe's advisory.
Exploitation context
Exploitation requires a victim to open a malicious file. The bundle marks the CVE as absent from KEV and provides no cited evidence of active exploitation or public exploit availability.
Researcher notes
The description says versions 15.1.0 and earlier, while the structured affected data lists boundaries through 15.1.2 with default unaffected status. Treat version scoping as unresolved until Adobe's advisory confirms it. No crash behavior, exposed data types, exploit availability, or specific fix is established by the bundle.
Mitigation direction
Consult Adobe's advisory to identify and install the vendor-confirmed corrected release.
Until remediated, prevent users from opening untrusted or unsolicited Substance 3D Designer files.
Use email and download controls to reduce delivery of suspicious Designer-compatible files.
Validation and detection
Inventory installed Substance 3D Designer versions across managed endpoints.
Compare detected versions with Adobe's current affected and corrected version guidance.
Confirm security controls restrict untrusted file delivery and opening.
After remediation, verify the installed version matches Adobe's vendor-confirmed corrected release.
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.