CVE-2025-54273: Adobe Substance3D – Viewer · Out-of-bounds Write
Affects Adobe Substance3D – ViewerSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 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 - Viewer | Affected
| Fixed in– |
AI-suggested
Until an official patch is released, organizations should implement strict controls on file sources by restricting Substance3D - Viewer usage to trusted files only. Employ application whitelisting and sandboxing techniques to limit the impact of potential exploitation. Educate users about the risks of opening files from untrusted or unknown sources, emphasizing caution with unsolicited 3D asset files. Monitor systems for unusual behavior indicative of exploitation attempts, such as unexpected process launches or memory anomalies. Consider network segmentation to isolate systems running Substance3D - Viewer from critical infrastructure. Regularly update endpoint protection solutions to detect potential exploit attempts. Once Adobe releases a patch, prioritize immediate deployment to eliminate the vulnerability.
Description
Substance3D - Viewer versions 0.25.2 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.