Skip to main content
VulnerabilityPublished Updated

CVE-2026-21341: 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, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% 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. Immediately restrict the opening of files from untrusted or unknown sources within Adobe Substance3D - Stager environments.
  2. Educate users on the risks of opening unsolicited or suspicious files, emphasizing verification of file origins.
  3. Implement application whitelisting and sandboxing to limit the impact of potential code execution.
  4. Monitor endpoint and network activity for unusual behaviors following file openings, such as unexpected process launches or network connections.
  5. Use endpoint detection and response (EDR) tools to detect exploitation attempts or memory corruption indicators.
  6. Coordinate with Adobe for timely patch deployment once an official fix is released; prioritize patching Substance3D - Stager installations.
  7. Employ network segmentation to isolate systems running Substance3D - Stager from critical infrastructure.
  8. Maintain regular backups of critical design assets to enable recovery in case of compromise.
  9. Review and enforce least privilege principles for users operating the software to minimize potential damage from exploitation.

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…