CVE-2025-6635
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 linked or imported into 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 confidenceThis vulnerability is an out-of-bounds read flaw in certain Autodesk products triggered by specially crafted PRT (Prototype/Part) files. When a user links or imports a malicious PRT file, the software attempts to read memory beyond allocated boundaries, potentially exposing sensitive data, causing a crash, or enabling arbitrary code execution in the current process context.
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.2CVSS 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 productsCheck your system for installed Autodesk applications that handle PRT files (such as AutoCAD, Inventor, or related products). Look in Program Files for Autodesk folders or check the Add/Remove Programs list.Affected if You have any Autodesk product installed that supports PRT file import or linking functionality.
-
Determine Autodesk Shared Components versionLocate the Autodesk Shared Components installation on your system. Check the version information for the component file (typically found in the Autodesk shared libraries folder). The specific affected version is 2026.2.Affected if The installed Autodesk Shared Components version is exactly 2026.2.
-
Verify PRT file handling is in useCheck recent file access history or document management systems for PRT file imports or links. PRT files (Prototype/Part files) are typically used in CAD workflows. Examine recent file open dialog histories or application recent files lists.Affected if You have recently linked or imported any PRT files, especially from untrusted or unknown sources.
-
Review application crash logsExamine system event logs, Autodesk application crash logs, or dump files for any crashes related to PRT file processing. Look for out-of-bounds memory access errors or access violation exceptions occurring during file operations.Affected if You observe crashes or access violations when processing PRT files, particularly from external or untrusted sources.
You are affected if you have Autodesk products with Shared Components version 2026.2 installed and have recently linked or imported PRT files from any source.
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 dataAvoid opening or importing PRT files from untrusted or unknown sources. Monitor for vendor patches from Autodesk and apply updates promptly. Implement file type restrictions and user awareness training to prevent handling of untrusted PRT files.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6635 — 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-6635 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