dbcve.org
AutocadApplication · Autodesk

CVE-2025-1650

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 CATPRODUCT file, when parsed through Autodesk AutoCAD, can force an Uninitialized Variable 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 confidence

An uninitialized variable vulnerability exists in Autodesk AutoCAD's parsing of CATPRODUCT files. When a user opens a maliciously crafted CATPRODUCT file, it triggers the uninitialized variable condition, which can be exploited to cause a denial-of-service crash, read sensitive data from process memory, or achieve arbitrary code execution within the context of the current AutoCAD process.

MitigationOrganizations should apply the latest Autodesk security updates for AutoCAD and implement user awareness training to avoid opening untrusted CATPRODUCT files from unknown 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
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 run the VER command or go to Help > About AutoCAD to see the exact product name and version. For other products (Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel), open the respective application and check its About dialog.
    Affected if The product is any of: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel.
  2. Determine the exact version number
    Note the full version string shown in the About dialog (for example: 2022.1.5, 2023.1.6, 2024.1.6, or 2025.1.1).
    Affected if The installed version is one of the affected products listed.
  3. Compare version against vulnerable ranges
    Check if the version falls within any of these vulnerable ranges: 2022 to <2022.1.6; 2023 to <2023.1.7; 2024 to <2024.1.7; 2025 to <2025.1.2.
    Affected if The installed version is lower than the first safe version in any of these ranges (2022.1.6, 2023.1.7, 2024.1.7, or 2025.1.2).
  4. Identify CATPRODUCT file usage
    Search for .CATPRODUCT files in your project directories or check recent file open history in AutoCAD (File > Recent).
    Affected if The user or organization works with CATPRODUCT files from CATIA or other CAD sources.

You are affected if you have any of the listed Autodesk products installed and the installed version falls below the safe version thresholds (2022.1.6, 2023.1.7, 2024.1.7, or 2025.1.2), especially if you open CATPRODUCT 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

Organizations should apply the latest Autodesk security updates for AutoCAD and implement user awareness training to avoid opening untrusted CATPRODUCT files from unknown sources.

Recommended fix High confidence

Upgrade to the following minimum versions: AutoCAD/verticals 2022.1.6+, 2023.1.7+, 2024.1.7+, 2025.1.2+

  1. Identify which affected Autodesk product(s) are installed (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel)
  2. Determine the current version of each installed product
  3. For products version 2022.x: upgrade to version 2022.1.6 or later
  4. For products version 2023.x: upgrade to version 2023.1.7 or later
  5. For products version 2024.x: upgrade to version 2024.1.7 or later
  6. For products version 2025.x: upgrade to version 2025.1.2 or later
  7. Obtain the update from the Autodesk Account portal or official Autodesk support website
  8. Install the update following Autodesk's standard installation procedure
Caveat Point updates typically do not introduce breaking changes; test critical workflows after upgrading

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,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 $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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