CVE-2025-54235: Adobe Substance3D – Modeler · Out-of-bounds Read
Affects Adobe Substance3D – ModelerSource 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 15% 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 12 Aug 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 - Modeler | Affected
| Fixed in– |
AI-suggested
European organizations should implement a multi-layered mitigation strategy: 1) Educate users about the risks of opening files from untrusted or unknown sources, emphasizing caution with files related to 3D modeling projects. 2) Restrict the use of Adobe Substance3D - Modeler to trusted environments and limit file sharing channels to verified sources. 3) Monitor and control local access to systems running the software to prevent unauthorized file introduction. 4) Employ application whitelisting and endpoint detection to identify anomalous file openings or suspicious behavior. 6) Maintain up-to-date backups and incident response plans to address potential data leaks. 7) Regularly check Adobe’s security advisories for patches or updates addressing this vulnerability and apply them promptly once released.
Description
Substance3D - Modeler versions 1.22.0 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. Exploitation of this issue requires user interaction in that a victim must open a malicious file.