CVE-2026-7454
published 2026-05-26CVE-2026-7454: A maliciously crafted WRL file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability. A malicious actor can leverage this…
PriorityP342high7.8CVSS 3.1
AVLACLPRNUIRSUCHIHAH
EPSS
0.13%
3.1th percentile
A maliciously crafted WRL file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| autodesk | 3ds_max | — | — |
| autodesk | 3ds_max | — | — |
| autodesk | 3ds_max | >= 2026 < 2026.1 | 2026.1 |
| autodesk | 3ds_max | >= 2027 < 2027.1 | 2027.1 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Autodesk 3ds Max up to 2026.0/2027.0 WRL File buffer overflow
vuldb·2026-05-26·CVSS 7.8
CVE-2026-7454 [HIGH] Autodesk 3ds Max up to 2026.0/2027.0 WRL File buffer overflow
A vulnerability, which was classified as critical, has been found in Autodesk 3ds Max up to 2026.0/2027.0. The impacted element is an unknown function of the component WRL File Handler. This manipulation causes buffer overflow.
The identification of this vulnerability is CVE-2026-7454. It is possible to initiate the attack remotely. There is no exploit available.
It is advisable to upgrade the affected component.
GHSA
GHSA-rcgw-6xcq-f735: A maliciously crafted WRL file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability
ghsa_unreviewed·2026-05-26
CVE-2026-7454 [HIGH] CWE-120 GHSA-rcgw-6xcq-f735: A maliciously crafted WRL file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability
A maliciously crafted WRL file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-05-26
Published