dbcve.org
AutocadApplication · Autodesk

CVE-2025-1428

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

This is an out-of-bounds read vulnerability in Autodesk AutoCAD's parser for CATPART files. When AutoCAD processes a maliciously crafted CATPART file, it reads memory beyond allocated buffer boundaries, potentially exposing sensitive data, causing crashes, or enabling arbitrary code execution in the current process context.

MitigationUsers should avoid opening untrusted CATPART files in AutoCAD until an official patch is available. Organizations should implement file validation and sandboxing for imported CAD files.

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 Windows Settings > Apps & Features, or check Program Files for folders named AutoCAD, Civil 3D, Advance Steel, or look in the Autodesk folder in Program Files
    Affected if The installed product is one of: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel
  2. Locate the product version
    In AutoCAD products, type _ABOUT or INFO at the command line, or right-click the application shortcut and select Properties to view the version field
    Affected if Version information is displayed showing a 4-digit year (2022, 2023, 2024, or 2025)
  3. Compare against affected version ranges
    Match the installed version to these vulnerable ranges: 2022 versions before 2022.1.6; 2023 versions before 2023.1.7; 2024 versions before 2024.1.7; 2025 versions before 2025.1.2
    Affected if The installed version 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
  4. Verify CATPART file handling capability
    Attempt to open a CATPART file using the standard FILEOPEN dialog, or check if CATIA or CATPART import plugins are listed in the application manage bindings or plugin list
    Affected if CATPART file import capability is present and enabled in the installation

The environment is affected if any of the 8 listed Autodesk products is installed with a version matching the vulnerable ranges and CATPART file handling is available.

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 CATPART files in AutoCAD until an official patch is available. Organizations should implement file validation and sandboxing for imported CAD files.

Recommended fix High confidence

Upgrade to version 2022.1.6 (for 2022 line), 2023.1.7 (for 2023 line), 2024.1.7 (for 2024 line), or 2025.1.2 (for 2025 line) depending on your product version

  1. 1. Identify the specific Autodesk product (e.g., AutoCAD, AutoCAD Architecture, Civil 3D, etc.) and the exact version number currently installed
  2. 2. Determine which version year (2022, 2023, 2024, or 2025) your installation belongs to
  3. 3. For AutoCAD 2022.x users: Upgrade to version 2022.1.6 or later
  4. 4. For AutoCAD 2023.x users: Upgrade to version 2023.1.7 or later
  5. 5. For AutoCAD 2024.x users: Upgrade to version 2024.1.7 or later
  6. 6. For AutoCAD 2025.x users: Upgrade to version 2025.1.2 or later
  7. 7. Download the appropriate updated version from Autodesk's official support website or through the Autodesk Desktop App
  8. 8. Install the update following standard Autodesk installation procedures
Caveat Autodesk point releases typically include bug fixes and security patches with minimal compatibility issues; users should review Autodesk's release notes for any specific considerations

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

Fix this in Autocad Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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