CVE-2026-21344: 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
Until Adobe releases an official patch, organizations should implement several specific mitigations: 1) Enforce strict file validation and scanning policies to detect and block malicious files before they reach end users. 2) Educate users about the risks of opening files from untrusted or unknown sources, emphasizing caution with unsolicited or unexpected 3D content files. 3) Use application whitelisting to restrict execution of unauthorized code and limit the privileges of Substance3D - Stager processes where possible. 4) Employ endpoint detection and response (EDR) solutions to monitor for suspicious behavior indicative of exploitation attempts. 5) Isolate systems running Substance3D - Stager from critical network segments to reduce lateral movement risk. 6) Regularly back up critical design assets to ensure recovery in case of compromise. 7) Monitor Adobe security advisories closely and apply patches promptly once available. These targeted actions go beyond generic advice by focusing on the specific attack vector (malicious file parsing) and the operational context of the affected software.
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.