dbcve.org
AutocadApplication · Autodesk

CVE-2025-1427

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 · high confidence

An uninitialized variable vulnerability exists in Autodesk AutoCAD's parser when processing CATPRODUCT files. A specially crafted CATPRODUCT file can trigger the uninitialized variable, potentially allowing an attacker to cause a crash, read sensitive data, or execute arbitrary code within the current AutoCAD process context.

MitigationAvoid opening CATPRODUCT files from untrusted or unknown sources. Apply vendor patches/updates from Autodesk once available. Run AutoCAD with reduced privileges to limit potential impact of code execution.

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 the installed Autodesk product
    Open AutoCAD or the specific vertical product (Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel). Go to Help > About Autodesk AutoCAD or check the title bar for the product name.
    Affected if The product name matches one of the affected products: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel.
  2. Find the installed version number
    In AutoCAD, type VER or ABOUT at the command line, or go to Help > About Autodesk AutoCAD. Note the full version string (for example, 2024.1.5).
    Affected if A version number is displayed that falls within any of these ranges: >=2022 and <2022.1.6, >=2023 and <2023.1.7, >=2024 and <2024.1.7, or >=2025 and <2025.1.2.
  3. Confirm CATPRODUCT file handling capability
    Verify the software can import or open CATPRODUCT files. Check if the import options or file open dialog includes CATPRODUCT as a supported file type, or attempt to open a test CATPRODUCT file.
    Affected if CATPRODUCT files can be opened or imported in the current installation (this is the default behavior in vulnerable versions).

You are affected if you have any of the listed Autodesk products installed with a version number in the affected ranges and CATPRODUCT file import is enabled (default).

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

Avoid opening CATPRODUCT files from untrusted or unknown sources. Apply vendor patches/updates from Autodesk once available. Run AutoCAD with reduced privileges to limit potential impact of code execution.

Recommended fix High confidence

Upgrade to AutoCAD 2022.1.6 / 2023.1.7 / 2024.1.7 / 2025.1.2 (or later) depending on your product year

  1. Identify the currently installed AutoCAD product and version (e.g., AutoCAD 2023, AutoCAD Architecture 2024, etc.)
  2. Determine which year/version line your installation belongs to from: 2022, 2023, 2024, or 2025
  3. For AutoCAD 2022: Upgrade to version 2022.1.6 or later
  4. For AutoCAD 2023: Upgrade to version 2023.1.7 or later
  5. For AutoCAD 2024: Upgrade to version 2024.1.7 or later
  6. For AutoCAD 2025: Upgrade to version 2025.1.2 or later
  7. Apply the same version thresholds to any vertical products (Architecture, Electrical, Mechanical, MEP, Plant 3D, Civil 3D, Advance Steel)
  8. Verify the installed version after upgrade matches or exceeds the required fixed version for your product line
Caveat Point releases in Autodesk products typically include bug fixes and security patches with minimal risk of breaking existing drawings or configurations

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

Fix this in Autocad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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