Crash and data corruption via excessive allocation
Published Jun 11, 2025 · Updated Aug 19, 2025
Excessive memory allocation in Autodesk Maya 2025 and USD plug-ins 0.31.0 and 0.10 allows attackers to crash or corrupt data via a crafted .usdc file. The .usdc parser uses file-controlled input to request excessive memory, but Autodesk has not identified the affected function or field. Exploitation requires a user to load the malicious file, after which the process can be interrupted or application data can be corrupted.
Summary
What happened
Excessive memory allocation in Autodesk Maya 2025 and USD plug-ins 0.31.0 and 0.10 allows attackers to crash or corrupt data via a crafted .usdc file. The .usdc parser uses file-controlled input to request excessive memory, but Autodesk has not identified the affected function or field. Exploitation requires a user to load the malicious file, after which the process can be interrupted or application data can be corrupted.
The record
- CVE
- CVE-2025-4605
- Published
- Jun 11, 2025
- Updated
- Aug 19, 2025
- Vendor
- Autodesk
- Product
- USD for 3ds Max
- Classifications
- CWE-770, CWE-789, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Max USD 0.10 <Max USD 0.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo