Skip to main content
VulnerabilityPublished Updated

CVE-2025-47108: 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:29 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 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

To mitigate CVE-2025-47108 effectively, organizations should implement a multi-layered approach: 1) Educate users about the risks of opening files from untrusted or unknown sources, emphasizing caution with files related to Substance3D - Painter. 2) Employ robust email and file scanning solutions to detect and quarantine suspicious files before they reach end users. 3) Restrict Substance3D - Painter usage to trusted networks and users with minimal necessary privileges to limit potential damage. 4) Utilize application whitelisting and sandboxing techniques to contain the execution of untrusted files and limit the impact of exploitation. 5) Monitor system and application logs for unusual behavior indicative of exploitation attempts. 6) Stay informed on Adobe’s security advisories and apply patches promptly once available. 7) Consider disabling or restricting the opening of external files within Substance3D - Painter if feasible until a patch is released. 8) Implement endpoint detection and response (EDR) tools capable of identifying exploitation patterns related to out-of-bounds writes and code execution.

Description

Substance3D - Painter versions 11.0.1 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…