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 access 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 Substance 3D Designer file may cause the application to read beyond intended memory boundaries, potentially exposing sensitive information. A victim must open the file, so the primary business risk is targeted delivery to designers or other users handling external assets.
Executive priority
Treat as a normal-priority confidentiality issue, with faster action for design teams receiving external files or accessing sensitive material. It is not supported as an emergency exploitation event, but version ambiguity makes prompt inventory and vendor-guidance review important.
Technical view
CVE-2026-21337 is a CWE-125 out-of-bounds read with CVSS 3.1 score 5.5. The vector indicates local attack delivery, low complexity, no privileges, required user interaction, and high confidentiality impact without documented integrity or availability impact.
Likely exposure
Exposure is most likely on endpoints running affected Substance 3D Designer versions where users open files from customers, contractors, shared repositories, email, or other untrusted sources. The supplied version data is inconsistent, so installed versions require confirmation against Adobe’s advisory.
Exploitation context
Exploitation requires a victim to open a malicious file. The bundle does not establish remote code execution, persistence, or system modification. The CVE is not listed as KEV, and the provided sources contain no evidence of active exploitation.
Researcher notes
The supplied description says versions 15.1.0 and earlier, while the structured affected entry lists 0 and 15.1.2 with default status unaffected. That representation is insufficient to establish a precise vulnerable range. Researchers should defer to Adobe APSB26-19 and avoid assuming 15.1.2 is affected or fixed.
Mitigation direction
Inventory Substance 3D Designer installations and identify their exact versions.
Check Adobe advisory APSB26-19 for the authoritative affected and remediated version ranges.
Apply Adobe’s documented update or mitigation after confirming applicability.
Limit opening of unsolicited or untrusted Substance 3D files pending remediation.
Use existing endpoint controls to scan and isolate suspicious files.
Validation and detection
Compare installed versions with the ranges stated in Adobe advisory APSB26-19.
Confirm managed endpoints received the approved Substance 3D Designer update.
Review software inventory for unmanaged or missed installations.
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.