NVD / CVE Program· CNA autodesk

CVE-2026-7452: WRL File Parsing Memory Corruption in Autodesk 3ds Max

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit No fix recorded

Published: May 26, 2026
Updated: Jul 24, 2026
EPSS: 0.1% · 5th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · autodesk: 7.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
autodesk	3ds max	cpe:2.3:a:autodesk:3ds_max

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

autodesk 3ds max2026
autodesk 3ds max2027

Versions reported by the vendor

Affected version ranges reported by the assigning authority (autodesk). Independent of NVD's CPE analysis and usually ahead of it.

Autodesk 3ds Max
- 2027 and later · before 2027.1affected
- 2026 and later · before 2026.1affected

Same product

autodesk: all records

Other highest-scoring records for the same primary product.

CVE-2009-3577Autodesk 3D Studio Max (3DSMax) 6 through 9 and 2008 through 2010 allows remote attackers to execute arbitrary code via a .max file with a M
39Monitor
CVE-2026-0661Out-of-Bounds Write in RGB File Parsing
33Monitor
CVE-2026-0660Stack Based Buffer Overflow in GIF File Parsing
33Monitor

Published before and after this one in the same product

← EarlierCVE-2026-7450May 26, 2026 · PAR File Parsing NULL Pointer Dereference in Autodesk 3ds Max
22Monitor
← EarlierCVE-2026-7451May 26, 2026 · TIF File Parsing Out-of-Bounds Write in Autodesk 3ds Max
31Monitor
Later →CVE-2026-7453May 26, 2026 · WRL File Parsing Memory Exhaustion in Autodesk 3ds Max
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-74540 days apartWRL File Parsing Memory Corruption in Autodesk 3ds Max
31Monitor
CVE-2026-1956890 days apartSVG File Parsing Memory Corruption Vulnerability in Autodesk 3ds Max
31Monitor
CVE-2025-6634293 days apartTGA File Parsing Memory Corruption Vulnerability
31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

AutodeskHackerOne · disclosure only (VDP)

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
No account or password is required.
A user must open a link or visit a page.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.autodesk.com/products/autodesk-access/overview

Show all references (1 more)

www.autodesk.com/trust/security-advisories/adsk-sa-2026-0006

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records