CVE-2025-4605
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAutodesk Maya contains an uncontrolled memory allocation vulnerability when parsing maliciously crafted .usdc (Universal Scene Description) files. When a user opens a specially crafted .usdc file, the software attempts to allocate memory without proper bounds checking, leading to excessive memory consumption that can cause denial of service or data corruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2025, < 2025.3.1= 0.10= 0.31.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Maya versionOpen Maya, go to Help > About Maya to view the full version number, or run 'maya.exe -version' from command lineAffected if Version is 2025.x where x is any build prior to 2025.3.1 (e.g., 2025.0, 2025.1, 2025.2)
-
Identify Universal Scene Description plugin versionCheck the USD plugin folder within Maya installation (typically at 'plug-ins/usd' or check Maya's plugin manager for USD version)Affected if USD version equals exactly 0.10 or 0.31.0
-
Verify USD file import capability is enabledCheck Maya plugin settings - ensure the 'usdImport' and 'usdExport' plugins are loaded, or verify USD is listed in the enabled file loadersAffected if USD import/export plugins are loaded and active in the Maya session
-
Inspect recent .usdc file activityCheck Maya's recent files list or system file explorer for recently opened .usdc files in the workspaceAffected if Any .usdc files were recently opened or are present in recent projects
You are affected if you run Maya version 2025.x (prior to 2025.3.1) OR use Universal Scene Description version 0.10 or 0.31.0, and you import or open .usdc files in your Maya environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2025.3.1
Users should avoid opening untrusted .usdc files in Maya. Implement file scanning and network segmentation for incoming files. Monitor Autodesk for security patches addressing this vulnerability.
Maya 2025.3.1 or later; Universal Scene Description newer than 0.31.0
- Upgrade Autodesk Maya to version 2025.3.1 or later
- For Universal Scene Description (USD), obtain a version newer than 0.31.0 that includes the security fix
- Ensure that any .usdc files loaded into Maya are from trusted sources
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4605 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4605 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data