# CVE-2025-4605: USD File Parsing Memory Allocation Vulnerability

> Attackers can cause denial of service or data corruption in Autodesk Maya by loading maliciously crafted USD files.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jun 2025
- **Updated:** 19 Aug 2025
- **Also known as:** GHSA-x8wm-pq66-9pp3

## What is CVE-2025-4605?

CVE-2025-4605 is a medium-severity denial of service vulnerability in Autodesk Maya, published on 11 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A maliciously crafted .usdc file, when loaded through Autodesk Maya, can force an uncontrolled memory allocation vulnerability. A malicious actor may leverage this vulnerability to cause a denial-of-service (DoS), or cause data corruption.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-789 (Memory Allocation with Excessive Size Value)

## Which versions are affected by CVE-2025-4605?

It affects 2 products.


Products: Autodesk Maya, Autodesk Universal Scene Description.

## How do I fix CVE-2025-4605?

No fix has been published for CVE-2025-4605 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-4605 being exploited?

There is no known exploitation of CVE-2025-4605 in the wild and no public exploit code.

## Other vulnerabilities in Autodesk Maya

- [CVE-2022-42947](https://insights.sbomify.com/CVE-2022-42947/): Memory corruption in Autodesk Maya (high 7.8)
- [CVE-2022-42946](https://insights.sbomify.com/CVE-2022-42946/): Memory corruption in Autodesk Maya (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4605 and fix it if it is affected.

What it is: CVE-2025-4605 is a medium-severity denial of service vulnerability in Autodesk Maya, published on 11 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-4605 in the wild and no public exploit code.

Affected product: Autodesk Maya. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-4605/ (Markdown: https://insights.sbomify.com/CVE-2025-4605/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4605
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4605
- OSV: https://osv.dev/vulnerability/CVE-2025-4605

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-4605/
Summaries are generated and may contain mistakes; the official description above is the record.