CVE-2025-54200: 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.1% chance of exploitation in 30 days – higher than 9% 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
1. Immediate mitigation involves user awareness training to avoid opening untrusted or unsolicited Substance3D model files, especially from unknown sources. 2. Implement strict file validation and sandboxing policies for handling 3D model files within the organization to contain potential exploitation. 3. Monitor Adobe's security advisories closely for patches or updates addressing this vulnerability and apply them promptly upon release. 4. Employ endpoint protection solutions capable of detecting anomalous behavior related to file processing in Substance3D - Modeler. 5. Restrict Substance3D - Modeler usage to trusted users and environments, and consider network segmentation to limit exposure. 6. Conduct regular security assessments and penetration testing focusing on file handling applications to identify similar vulnerabilities proactively.
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.