Skip to main content
VulnerabilityPublished

CVE-2025-54197: Adobe Substance3D – Modeler · Out-of-bounds Read

Affects Adobe Substance3D – ModelerSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Adobe Substance3D - ModelerAffected
  • =0
Fixed in–

AI-suggested

To mitigate the risk posed by CVE-2025-54197, European organizations should implement several targeted measures beyond generic advice: 1) Enforce strict file handling policies restricting the opening of Substance3D - Modeler files from untrusted or unknown sources, including email attachments and downloads. 2) Educate users on the risks of opening unsolicited or suspicious 3D model files and implement phishing awareness training tailored to creative teams. 3) Utilize endpoint security solutions capable of sandboxing or scanning 3D model files for malicious content before allowing them to be opened. 4) Monitor and restrict the use of Substance3D - Modeler to trusted personnel and environments, potentially isolating the application in virtualized or containerized setups to limit memory exposure. 5) Maintain up-to-date backups and incident response plans specifically addressing potential data leakage scenarios. 6) Engage with Adobe for timely updates and patches, and plan for rapid deployment once available. 7) Implement Data Loss Prevention (DLP) tools to detect and prevent unauthorized exfiltration of sensitive data that could result from memory disclosure. These steps collectively reduce the attack surface and limit the potential impact of exploitation.

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.

References

Community reviews

Loading reviews…