Skip to main content
VulnerabilityPublished Updated

CVE-2026-21342: Adobe Substance3D – Stager · Out-of-bounds Write

Affects Adobe Substance3D – StagerSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AdobeSubstance3D - StagerAffected
  • <=3.1.6
Fixed in–

AI-suggested

  1. Monitor Adobe’s official channels for patches or updates addressing CVE-2026-21342 and apply them promptly once released.
  2. Implement strict file handling policies restricting the opening of files from untrusted or unknown sources within Substance3D - Stager.
  3. Educate users on the risks of opening unsolicited or suspicious files, emphasizing phishing and social engineering awareness.
  4. Employ endpoint protection solutions capable of detecting anomalous behaviors associated with memory corruption or code execution attempts in Adobe applications.
  5. Use application whitelisting and sandboxing techniques to limit the execution scope of Substance3D - Stager and contain potential exploitation.
  6. Regularly back up critical design files and digital assets to enable recovery in case of compromise.
  7. Monitor logs and network traffic for unusual activity related to the application to detect early signs of exploitation attempts.
  8. Consider network segmentation to isolate systems running Substance3D - Stager from sensitive infrastructure to limit lateral movement if compromised.

Description

Substance3D - Stager versions 3.1.6 and earlier are affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

References

Community reviews

Loading reviews…