CVE-2025-54262: Adobe Substance3D – Stager · Out-of-bounds Read
Affects Adobe Substance3D – StagerSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% 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 16 Sep 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 - Stager | Affected
| Fixed in– |
AI-suggested
Organizations should implement the following specific mitigations: 1) Monitor Adobe’s official channels for patches and apply updates to Substance3D - Stager as soon as they become available. 2) Enforce strict file validation and scanning policies for all files opened in Substance3D - Stager, including sandboxing or opening files in isolated environments when possible. 3) Educate users about the risks of opening files from untrusted or unknown sources, emphasizing caution with unsolicited or suspicious files. 4) Employ endpoint detection and response (EDR) solutions to monitor for anomalous behavior indicative of exploitation attempts. 5) Restrict user privileges to the minimum necessary to reduce the impact of code execution under user context. 6) Consider network segmentation to isolate design workstations from critical infrastructure to limit lateral movement in case of compromise. 7) Maintain regular backups of critical design data to enable recovery in case of disruption.
Description
Substance3D - Stager versions 3.1.3 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.