dbcve.org
AutocadApplication · Autodesk

CVE-2025-1431

HIGH · 7.8 CVSS v3.1 Published 2025-03-13
Fix available
A fix is available. Upgrade to 2022.1.6 / 2023.1.7 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A maliciously crafted SLDPRT file, when parsed through Autodesk AutoCAD, 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 · high confidence

AutoCAD contains an out-of-bounds read vulnerability when parsing maliciously crafted SLDPRT (SolidWorks part) files. The vulnerability occurs during file parsing operations where improper bounds checking allows reading memory beyond allocated buffers. This can be leveraged to cause a denial of service (crash), expose sensitive process memory contents, or achieve arbitrary code execution in the context of the running AutoCAD process.

MitigationApply vendor-supplied patches for AutoCAD when available. Avoid opening SLDPRT files from untrusted or unknown sources, and consider disabling file preview/thumbnail features in AutoCAD to prevent automatic parsing.

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
AutocadApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad ArchitectureApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad ElectricalApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad MechanicalApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad MepApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Autocad Plant 3dApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Civil 3dApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2
Advance SteelApplication
Affected:>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Autodesk product
    Open AutoCAD and go to Help > About, or check Add/Remove Programs for installed Autodesk software. Look for product name (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel).
    Affected if Any of the affected products listed in the CVE is installed.
  2. Check installed version number
    In AutoCAD, type VERSION at the command line, or check the installed program version in Add/Remove Programs. Note the full version including any service pack or update numbers.
    Affected if Version is 2022.x, 2023.x, 2024.x, or 2025.x where x falls within the vulnerable ranges.
  3. Compare version to affected ranges
    Match your installed version against: 2022 < 2022.1.6, 2023 < 2023.1.7, 2024 < 2024.1.7, 2025 < 2025.1.2. Any version within these ranges is vulnerable.
    Affected if Installed version is lower than the fixed versions listed (e.g., 2022.1.5 or earlier, 2023.1.6 or earlier, etc.).
  4. Determine SLDPRT file usage
    Check if users import or open SolidWorks part files (.sldPRT). Search for .sldPRT file associations in Windows registry under HKEY_CLASSES_ROOT\.sldPRT, or ask users if they work with these files.
    Affected if Users open or import SLDPRT files in AutoCAD.

The environment is affected if any of the listed AutoCAD products is installed with a version falling below the fixed releases (2022.1.6, 2023.1.7, 2024.1.7, 2025.1.2) AND users process SLDPRT files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022.1.6 / 2023.1.7 / 2024.1.7 or later
Fixed in 2022.1.62023.1.72024.1.7
Interim mitigation

Apply vendor-supplied patches for AutoCAD when available. Avoid opening SLDPRT files from untrusted or unknown sources, and consider disabling file preview/thumbnail features in AutoCAD to prevent automatic parsing.

Recommended fix Moderate confidence

Upgrade to AutoCAD and related products versions 2022.1.6, 2023.1.7, 2024.1.7, or 2025.1.2 (or later) depending on your product line

  1. Identify the specific Autodesk product and version currently installed from the Help > About menu
  2. Navigate to the Autodesk Account portal at accounts.autodesk.com
  3. Download the appropriate update based on your product line: For 2022 versions, obtain version 2022.1.6 or later; For 2023 versions, obtain version 2023.1.7 or later; For 2024 versions, obtain version 2024.1.7 or later; For 2025 versions, obtain version 2025.1.2 or later
  4. Close all running instances of the Autodesk application
  5. Run the installer with administrator privileges
  6. Follow the on-screen installation prompts to complete the update
  7. Verify the installed version matches the target fixed version by checking Help > About
Caveat Review Autodesk release notes for your target version to check for potential workflow changes, deprecated features, or compatibility considerations with custom scripts/LISP routines

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Autocad Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1431 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1431 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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