dbcve.org
AutocadApplication · Autodesk

CVE-2025-1649

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 in Autodesk AutoCAD occurs when parsing maliciously crafted CATPRODUCT files. This memory corruption issue can be exploited to cause a denial of service (crash), read sensitive data from process memory, or achieve arbitrary code execution within the current process context.

MitigationApply vendor-supplied patches from Autodesk when released; avoid opening untrusted or unknown CATPRODUCT files in AutoCAD until the vulnerability is patched.

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
    Check if AutoCAD or any vertical product (Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel) is installed. Look in Program Files or the application menu.
    Affected if Any of these products are installed, proceed to version check.
  2. Find installed product version
    Open the application and go to Help > About, or right-click the main executable and select Properties > Details to view the version number.
    Affected if Version number is displayed (for example, 2022.x, 2023.x, 2024.x, or 2025.x).
  3. Compare version against affected ranges
    Match your installed version to these vulnerable ranges: 2022 versions < 2022.1.6; 2023 versions < 2023.1.7; 2024 versions < 2024.1.7; 2025 versions < 2025.1.2
    Affected if Your installed version falls within any of these ranges.
  4. Confirm vulnerability trigger condition
    This vulnerability triggers when AutoCAD parses a maliciously crafted CATPRODUCT file. The file format must be present and opened for exploitation.
    Affected if You open or import CATPRODUCT files in your AutoCAD environment.

If you have an affected product version AND open CATPRODUCT files, your environment is potentially vulnerable to this CVE.

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 from Autodesk when released; avoid opening untrusted or unknown CATPRODUCT files in AutoCAD until the vulnerability is patched.

Recommended fix Moderate confidence

Upgrade to the following minimum versions based on your product year: AutoCAD 2022.1.6 or later, AutoCAD 2023.1.7 or later, AutoCAD 2024.1.7 or later, or AutoCAD 2025.1.2 or later (applies to all listed vertical products)

  1. 1. Identify the exact version of the installed Autodesk product (AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel) by opening the application and checking Help > About AutoCAD or the application's info dialog
  2. 2. Based on the installed version year (2022, 2023, 2024, or 2025), determine the minimum security update version required: 2022.1.6, 2023.1.7, 2024.1.7, or 2025.1.2 respectively
  3. 3. Access the Autodesk Support portal or product updates page at www.autodesk.com to download the appropriate security update for your product version
  4. 4. Close all Autodesk applications and any related processes
  5. 5. Run the downloaded installer and follow the prompts to apply the security update
  6. 6. Verify the installation was successful by checking the product version again confirms it meets or exceeds the minimum fixed version for your release year
Caveat Standard Autodesk update considerations apply - review release notes for your specific version to check for workflow or compatibility impacts with custom scripts, plugins, or older file formats

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

Fix this in Autocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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