Skip to main content
CVE-2026-126826VulnerabilityPublished

A maliciously crafted SBSAR file, when imported or loaded through the Substance in 3ds Max plugin in Autodesk 3ds Max

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-126826· High 7.8

Not known to be exploited · CVSS 7.8 High : upgrade to 2027.3.0 soon.

Data as of 19 Nov 2026, 16:40 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (autodesk)CVSS 3.17.8
Patch
Available – fixed in 2027.3.0
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 19 Nov 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 18 Nov 2026.

What to do

Upgrade 3ds Max to 2027.3.0.

Affected software

ProductAffectedFixed in
Autodesk3ds MaxAffected
  • >=2027.0.0 <2027.3.0
Fixed in
  • 2027.3.0

AI-suggested

If you cannot patch yet, avoid importing or loading untrusted SBSAR files in the Substance plugin for Autodesk 3ds Max 2027.

Description

A vulnerability exists in the Substance in 3ds Max plugin for Autodesk 3ds Max 2027 where a maliciously crafted SBSAR file can trigger an Out-of-Bounds Write. This can lead to application crashes, data corruption, or potentially arbitrary code execution within the context of the current process.

References

Community reviews

Loading reviews…