CVE-2026-7450

CVE-2026-7450 is a medium-severity vulnerability in Autodesk 3ds Max with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-476.

Key facts

Description

A maliciously crafted PAR file, when parsed through Autodesk 3ds Max, can force a NULL Pointer Dereference vulnerability. Successful exploitation may cause the application to crash, leading to a denial-of-service condition.

Frequently asked questions

What is CVE-2026-7450?
A maliciously crafted PAR file, when parsed through Autodesk 3ds Max, can force a NULL Pointer Dereference vulnerability. Successful exploitation may cause the application to crash, leading to a denial-of-service condition.
How severe is CVE-2026-7450?
CVE-2026-7450 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-7450 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-7450?
CVE-2026-7450 primarily affects Autodesk 3ds Max. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-7450?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-7450 have an EU (EUVD) identifier?
Yes. CVE-2026-7450 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-31909.
When was CVE-2026-7450 published?
CVE-2026-7450 was published on 2026-05-26 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Autodesk 3ds Max

All CVEs affecting Autodesk 3ds Max →

Other CWE-476 (NULL Pointer Dereference) vulnerabilities

Browse all CWE-476 (NULL Pointer Dereference) vulnerabilities →