CVE-2025-9454
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 PRT file, when parsed through certain Autodesk products, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.
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 confidenceAn out-of-bounds read vulnerability exists in multiple Autodesk products when parsing maliciously crafted PRT files. The vulnerability allows a remote attacker to read beyond allocated memory boundaries, potentially leading to sensitive data disclosure, denial of service (crash), or arbitrary code execution in the context of the current process.
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< 2026.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 Autodesk productsReview installed software on the system to find any Autodesk applications such as AutoCAD, Revit, 3ds Max, Maya, or other products that utilize Autodesk Shared Components.Affected if Any Autodesk product that uses Autodesk Shared Components is installed on the system.
-
Check Autodesk Shared Components versionLocate and examine the version of the Autodesk Shared Components installation. This is typically found within the installation directory of Autodesk products or via the program's version information (right-click the executable, select Properties, view Version tab). Compare the version number to the threshold of 2026.5.Affected if The installed version of Autodesk Shared Components is lower than 2026.5.
-
Determine PRT file processing usageIdentify whether the system or users routinely process PRT (Parameter) files, which are used by Autodesk applications. Check for recent PRT file activity in document directories, network shares, or download folders.Affected if Users or automated processes handle or open PRT files from external or untrusted sources.
-
Review recent crash logs or error reportsSearch system event logs, application event logs, or Autodesk crash dump files for any recent anomalies or out-of-bounds read errors related to PRT file parsing.Affected if There are crash logs or error reports indicating failures when opening PRT files.
The environment is affected if Autodesk Shared Components version 2026.5 or lower is installed and users process PRT files from potentially untrusted sources.
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.
From vendor data2026.5
Users should avoid opening untrusted or unverified PRT files from unknown sources. Apply vendor patches from Autodesk when available, and consider implementing file validation or sandboxing for PRT file processing.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9454 — 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-9454 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