CVE-2025-54205: Adobe Substance3D – Sampler · Out-of-bounds Read
Affects Adobe Substance3D – SamplerSource 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 - Sampler | Affected
| Fixed in– |
AI-suggested
Organizations should implement strict file handling policies, including restricting the opening of files from untrusted or unknown sources within Adobe Substance3D - Sampler. Employing sandboxing or isolated environments for opening files can limit exposure. Monitoring and educating users about spear-phishing and malicious file risks is critical. Since no patches are currently available, consider temporarily limiting the use of affected versions or substituting with alternative tools where feasible. Network segmentation and endpoint detection solutions can help identify anomalous behaviors related to file handling. Additionally, organizations should maintain up-to-date backups and incident response plans tailored to data leakage scenarios. Close coordination with Adobe for timely patch deployment once available is essential.
Description
Substance3D - Sampler versions 5.0.3 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.