Skip to main content
VulnerabilityPublished Updated

CVE-2026-27273: Adobe Substance3D – Stager · Out-of-bounds Write

Affects Adobe Substance3D – StagerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High.

Data as of 30 Oct 2026, 06:59 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 3% 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 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AdobeSubstance3D - StagerAffected
  • <=3.1.7
Fixed in–

AI-suggested

To mitigate CVE-2026-27273, organizations should implement the following specific measures: 1) Immediately restrict the opening of files from untrusted or unknown sources within Adobe Substance3D - Stager environments. 2) Employ application whitelisting and sandboxing techniques to limit the ability of the application to execute arbitrary code or affect other system components. 3) Use endpoint detection and response (EDR) tools to monitor for suspicious behaviors indicative of exploitation attempts, such as anomalous memory writes or process injections related to Substance3D - Stager. 4) Educate users about the risks of opening files from unverified sources and implement strict email filtering to reduce the likelihood of malicious file delivery. 5) Regularly back up critical data to enable recovery in case of compromise. 6) Monitor Adobe’s security advisories closely and apply patches or updates as soon as they become available. 7) Consider deploying network segmentation to isolate systems running Substance3D - Stager from sensitive parts of the network to limit lateral movement. These targeted actions go beyond generic advice and address the specific exploitation vector and environment of this vulnerability.

Description

Substance3D - Stager versions 3.1.7 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…