Skip to main content
VulnerabilityPublished Updated

CVE-2025-43581: Adobe Substance3D – Sampler · Out-of-bounds Write

Affects Adobe Substance3D – SamplerSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 14:05 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 18% 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 - SamplerAffected
  • =0
Fixed in–

AI-suggested

To mitigate CVE-2025-43581, organizations should implement the following specific measures: 1) Monitor Adobe's official channels for patches and apply updates immediately upon release to eliminate the vulnerability. 2) Restrict the opening of Substance3D - Sampler files from untrusted or unknown sources by enforcing strict file validation and sandboxing techniques. 3) Educate users about the risks of opening files from unverified origins and implement phishing awareness training to reduce the likelihood of social engineering attacks. 4) Employ application whitelisting and endpoint protection solutions that can detect and block suspicious behaviors related to memory corruption exploits. 5) Use network segmentation to isolate systems running Substance3D - Sampler, limiting lateral movement in case of compromise. 6) Regularly back up critical project data and maintain incident response plans tailored to creative software environments. 7) Consider deploying runtime application self-protection (RASP) or memory protection technologies that can detect out-of-bounds writes at runtime. These targeted actions go beyond generic advice by focusing on controlling file sources, user behavior, and advanced detection mechanisms specific to this vulnerability type.

Description

Substance3D - Sampler versions 5.0 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…