dbcve.org
AutocadApplication · Autodesk

CVE-2025-1652

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 MODEL 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

A maliciously crafted MODEL file parsed by Autodesk AutoCAD triggers an out-of-bounds read vulnerability. This memory safety flaw allows a remote attacker to potentially read sensitive data from process memory, cause a denial-of-service crash, or achieve arbitrary code execution within the context of the AutoCAD process.

MitigationUsers should avoid opening untrusted or unfamiliar MODEL files and apply the vendor patch from Autodesk when released. Organizations should implement file integrity controls and restrict MODEL file execution from untrusted sources.

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
Advance SteelApplication
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
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
Autocad Map 3dApplication
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

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 the application and go to Help > About Autodesk [Product Name], or type 'ABOUT' in the command line and press Enter. The dialog will display the exact product name and version number.
    Affected if The product is one of: AutoCAD, Advance Steel, Civil 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, AutoCAD Map 3D, or AutoCAD Architecture.
  2. Determine the exact version number
    Note the full version string shown in the About dialog (for example: 2024.1.5 or 2023.1.6). Record the three-digit version number (year.release.update).
    Affected if A version number is displayed.
  3. Compare version against affected ranges
    Check if the installed version falls into any of these ranges: 2022.x.x but less than 2022.1.6; 2023.x.x but less than 2023.1.7; 2024.x.x but less than 2024.1.7; 2025.x.x but less than 2025.1.2.
    Affected if The installed version is within any of these ranges.
  4. Verify MODEL file handling is possible
    Confirm the system can open .MODEL file extensions. This is the native file format parsed by the affected component. Check if the application has file association for .MODEL or if users routinely import such files.
    Affected if The product is used to open or import MODEL files from external sources.

The environment is affected if any of the listed Autodesk products is installed with a version matching the ranges above and users open MODEL files from untrusted sources.

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

Users should avoid opening untrusted or unfamiliar MODEL files and apply the vendor patch from Autodesk when released. Organizations should implement file integrity controls and restrict MODEL file execution from untrusted sources.

Recommended fix High confidence

Upgrade to version 2022.1.6 (or later) for 2022 products, 2023.1.7 (or later) for 2023 products, 2024.1.7 (or later) for 2024 products, or 2025.1.2 (or later) for 2025 products

  1. 1. Identify the installed Autodesk product (AutoCAD, Advance Steel, Civil 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, AutoCAD Map 3D, or AutoCAD Architecture) and its current version number
  2. 2. Determine which version line the installation belongs to (2022, 2023, 2024, or 2025)
  3. 3. Download the appropriate fixed version from the Autodesk Account portal or Autodesk's official support website: for 2022 line upgrade to 2022.1.6, for 2023 line upgrade to 2023.1.7, for 2024 line upgrade to 2024.1.7, for 2025 line upgrade to 2025.1.2
  4. 4. Uninstall the current vulnerable version through Windows Control Panel or the Autodesk uninstaller
  5. 5. Restart the system after uninstallation
  6. 6. Install the downloaded fixed version following the on-screen installation wizard
  7. 7. Apply any available updates or service packs after initial installation
  8. 8. Verify the installation was successful and test with sample MODEL files
Caveat Standard AutoCAD upgrade considerations apply: verify custom scripts, Lisp routines, and third-party plugins are compatible with the new version; back up user settings and customizations before upgrade

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1652 — 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-1652 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