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
Adobe Substance 3D Designer can expose sensitive information from memory when a user opens a malicious file. The issue does not reportedly modify data or disrupt service, but leaked memory could contain confidential material. User interaction and local file access reduce urgency compared with remotely exploitable flaws.
Executive priority
Treat as a normal, time-bounded desktop remediation rather than an emergency. Prioritize teams handling external design files or sensitive projects. Escalate if Adobe reports exploitation or internal telemetry identifies targeted malicious-file delivery.
Technical view
CVE-2026-21339 is a CWE-125 out-of-bounds read. CVSS 3.1 is 5.5 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), indicating potentially high confidentiality impact without integrity or availability impact. The supplied version data is inconsistent: the description says 15.1.0 and earlier, while structured data references 15.1.2.
Likely exposure
Workstations using affected Substance 3D Designer releases and opening untrusted project or asset files are most exposed. Prioritize designers receiving files through email, collaboration platforms, downloads, or external contributors. Confirm affected versions with Adobe because the supplied version statements conflict.
Exploitation context
Exploitation requires a victim to open a malicious file locally; no privileges are required. The supplied record marks the CVE as absent from KEV and provides no evidence of active exploitation. KEV absence does not prove exploitation is not occurring.
Researcher notes
The documented outcome is memory disclosure through an out-of-bounds read after malicious-file processing. Available evidence does not identify the file format, exposed memory contents, root cause, or reliable detection indicators. Avoid assuming code execution. Version scope requires confirmation from Adobe due to conflicting bundle fields.
Mitigation direction
Consult Adobe advisory APSB26-19 and apply the vendor-recommended update or remediation.
Restrict opening Substance 3D files from unknown or untrusted sources.
Use attachment filtering and endpoint controls to reduce delivery of suspicious design files.
Isolate higher-risk file review from systems handling sensitive information where practical.
Validation and detection
Inventory installed Substance 3D Designer versions across managed endpoints.
Reconcile detected versions against Adobe advisory APSB26-19 because supplied affected-version data conflicts.
Verify the vendor-recommended remediation is deployed and persists after software updates.
Review security telemetry for suspicious design-file delivery and unexpected application behavior.
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.