Skip to main content
VulnerabilityPublished

CVE-2025-21166: Adobe Substance3D – Designer · Out-of-bounds Write

Affects Adobe Substance3D – DesignerSource 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 14% 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 8 Jul 2025

  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
Adobe Substance3D - DesignerAffected
  • =0
Fixed in–

AI-suggested

  1. Implement strict file handling policies: Educate users to avoid opening untrusted or unsolicited files, especially those purporting to be Adobe Substance3D project files or assets.
  2. Employ application whitelisting and sandboxing: Run Adobe Substance3D - Designer within controlled environments or sandboxes to limit the impact of potential exploitation.
  3. Use endpoint detection and response (EDR) solutions: Monitor for anomalous behaviors indicative of exploitation attempts, such as unexpected memory writes or process injections related to the Substance3D application.
  4. Network segmentation: Isolate systems running Substance3D to limit lateral movement if compromise occurs.
  5. Monitor for updates from Adobe: Although no patches are currently available, organizations should prioritize applying official fixes as soon as they are released.
  6. Implement email and web filtering: Block or flag potentially malicious files and links that could be used to deliver exploit payloads.
  7. Maintain regular backups of critical project files and assets to enable recovery in case of compromise.
  8. Conduct targeted phishing awareness campaigns focusing on the risks of opening malicious design files. These measures, combined, reduce the likelihood of exploitation and limit potential damage until a patch is available.

Description

Substance3D - Designer versions 14.1 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…