CVE-2025-21167: Adobe Substance3D – Designer · Out-of-bounds Read
Affects Adobe Substance3D – DesignerSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- 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:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2025
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 |
|---|---|---|
| Adobe Substance3D - Designer | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should: 1) Immediately update Adobe Substance3D - Designer to the latest version once Adobe releases a patch addressing CVE-2025-21167. 2) Until a patch is available, implement strict file handling policies, including restricting the opening of untrusted or unsolicited Substance3D files. 3) Educate users about the risks of opening files from unknown or unverified sources, emphasizing the need for caution with email attachments or downloads. 4) Employ endpoint security solutions capable of detecting and blocking suspicious file activities related to Substance3D. 5) Monitor network and endpoint logs for unusual behavior that could indicate exploitation attempts. 6) Consider application whitelisting or sandboxing Substance3D to limit the impact of potential exploitation. These steps go beyond generic advice by focusing on controlling file trust boundaries and user behavior specific to this vulnerability.
Description
Substance3D - Designer versions 14.1 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. Exploitation of this issue requires user interaction in that a victim must open a malicious file.