CVE-2025-61833: 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 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% 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 11 Nov 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Adobe Substance3D - Stager | Affected
| Fixed in– |
AI-suggested
Until an official patch is released, organizations should implement strict controls on file sources and user behavior, including disabling or restricting the opening of untrusted or unsolicited files in Substance3D - Stager. Employ application whitelisting and sandboxing to limit the impact of potential exploits. Use endpoint detection and response (EDR) tools to monitor for suspicious activity related to Substance3D - Stager processes. Educate users about the risks of opening files from unknown or untrusted sources. Network segmentation can help contain potential breaches. Once Adobe releases a patch, prioritize immediate deployment. Additionally, consider employing file integrity monitoring on critical design files and maintaining regular backups to recover from potential compromises.
Description
Substance3D - Stager versions 3.1.5 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.