Skip to main content
VulnerabilityPublished Updated

CVE-2025-54187: Adobe Substance3D – Painter · Out-of-bounds Write

Affects Adobe Substance3D – PainterSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 12:55 UTC

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

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 - PainterAffected
  • =0
Fixed in–

AI-suggested

Until Adobe releases an official patch, organizations should implement several specific mitigations: 1) Enforce strict file handling policies by restricting the opening of Substance3D - Painter project files to trusted sources only. 2) Educate users about the risks of opening files from unverified or unknown origins, emphasizing caution with email attachments and downloads. 3) Employ application whitelisting and sandboxing techniques to limit the impact of potential exploitation. 4) Monitor endpoint behavior for unusual activity related to Substance3D - Painter processes, such as unexpected memory usage or network connections. 5) Use endpoint detection and response (EDR) tools to detect and block exploit attempts. 6) Maintain up-to-date backups of critical data to enable recovery in case of compromise. 7) Prepare to deploy patches promptly once Adobe releases them, and test updates in controlled environments before widespread deployment. 8) Consider network segmentation to isolate systems running Substance3D - Painter from sensitive infrastructure to limit lateral movement.

Description

Substance3D - Painter versions 11.0.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.

References

Community reviews

Loading reviews…