CVE-2026-21343: Adobe Substance3D – Stager · Out-of-bounds Read
Affects Adobe Substance3D – StagerSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AdobeSubstance3D - Stager | Affected
| Fixed in– |
AI-suggested
Organizations should implement the following specific mitigations: 1) Monitor Adobe's official channels for patches addressing this vulnerability and apply updates promptly once available. 2) Enforce strict file handling policies, including disabling or restricting the opening of untrusted or unsolicited 3D files within Substance3D - Stager. 3) Employ endpoint protection solutions capable of detecting anomalous behaviors or memory corruption attempts related to out-of-bounds reads. 4) Educate users on the risks of opening files from unknown or untrusted sources, emphasizing phishing and social engineering awareness. 5) Utilize application whitelisting to limit execution of unauthorized code and sandbox Substance3D - Stager where feasible to contain potential exploitation. 6) Implement network segmentation to reduce the impact of a compromised workstation. 7) Conduct regular security assessments and monitor logs for suspicious activity related to Substance3D processes. These targeted steps go beyond generic advice by focusing on the specific attack vector and software context.
Description
Substance3D - Stager versions 3.1.6 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.