dbcve.org
AutocadApplication · Autodesk

CVE-2025-1433

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

A file parsing vulnerability exists in Autodesk AutoCAD where a maliciously crafted MODEL file triggers an out-of-bounds memory read. An attacker can exploit this to crash the application, expose sensitive process memory, or potentially achieve arbitrary code execution within the current process context.

MitigationApply the vendor patch when released by Autodesk. Until then, only open MODEL files from trusted sources and consider running AutoCAD in an isolated environment to limit potential impact.

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 AutoCAD product
    Open AutoCAD and go to Help > About Autodesk AutoCAD, or check Add/Remove Programs for installed Autodesk products. Look for one of: AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel.
    Affected if Any of these 8 products are installed, proceed to version check.
  2. Determine installed version number
    In AutoCAD, type VERSION or VER at the command line, or check Help > About. The version displays as a number like 2022.1.5, 2023.1.6, 2024.1.6, or 2025.1.1.
    Affected if A version number is displayed, proceed to range comparison.
  3. Compare version to affected ranges
    Check if your version falls into any of these ranges: 2022.x where x < 1.6; 2023.x where x < 1.7; 2024.x where x < 1.7; 2025.x where x < 1.2. For example, 2022.1.5 is affected (less than 2022.1.6), 2023.1.7 is not affected (equal to threshold).
    Affected if Your installed version is less than the first safe version in any of the four year ranges.
  4. Confirm vulnerable feature present
    This vulnerability is triggered when opening a MODEL file. MODEL files are a native AutoCAD file format. Verify that your installation includes DWG/MODEL file handling by attempting to open any existing .dwg or .model file, or check that the file type association exists in Windows.
    Affected if AutoCAD can open MODEL files, meaning the vulnerable parsing code is present in your installation.

If your installed AutoCAD product version is 2022.1.5 or earlier, 2023.1.6 or earlier, 2024.1.6 or earlier, or 2025.1.1 or earlier, your environment is affected by this vulnerability.

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 the vendor patch when released by Autodesk. Until then, only open MODEL files from trusted sources and consider running AutoCAD in an isolated environment to limit potential impact.

Recommended fix High confidence

Upgrade to the following minimum versions: AutoCAD/Civil 3D/etc. 2022.1.6, 2023.1.7, 2024.1.7, or 2025.1.2 (depending on your version year)

  1. 1. Identify the current version of the installed Autodesk product by opening the application and navigating to Help > About AutoCAD (or the equivalent for your product)
  2. 2. Determine your product line (AutoCAD, Civil 3D, AutoCAD Architecture, etc.) and version year (2022, 2023, 2024, or 2025)
  3. 3. For AutoCAD 2022: Upgrade to version 2022.1.6 or later
  4. 4. For AutoCAD 2023: Upgrade to version 2023.1.7 or later
  5. 5. For AutoCAD 2024: Upgrade to version 2024.1.7 or later
  6. 6. For AutoCAD 2025: Upgrade to version 2025.1.2 or later
  7. 7. Download the appropriate update from Autodesk's official support website (autodesk.com) or use the Autodesk Access/Device Manager to check for and install updates
  8. 8. Back up any critical drawings and custom settings before applying the update
Caveat Standard Autodesk update; back up drawings and custom settings before upgrading as a precaution

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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