CVE-2025-1429
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 · uneditedA maliciously crafted MODEL file, when parsed through Autodesk AutoCAD, can force a Heap-Based Overflow 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 confidenceA heap-based buffer overflow vulnerability exists in Autodesk AutoCAD when parsing maliciously crafted MODEL files. An attacker can exploit this to potentially execute arbitrary code, crash the application, or read sensitive data from the process memory.
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>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2022, < 2022.1.6>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed AutoCAD product and versionOpen Windows Control Panel > Programs and Features, or right-click the AutoCAD/vertical product shortcut and select Properties, to view the installed version number (for example, 2024.0.1 or 2025.1.0)Affected if The version falls within any of these ranges: 2022.x to <2022.1.6; 2023.x to <2023.1.7; 2024.x to <2024.1.7; 2025.x to <2025.1.2
-
Confirm the specific AutoCAD vertical product if applicableCheck the program name in the Start menu or Programs and Features list (such as AutoCAD Architecture 2024, AutoCAD Electrical 2023, Civil 3D 2025, or Advance Steel 2022)Affected if The product is one of AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D, Civil 3D, or Advance Steel with a version matching the affected ranges
-
Verify the vulnerability trigger conditionThis flaw is triggered only when AutoCAD opens a specially crafted MODEL file (a .dwg file with MODEL space content or a standalone MODEL file format)Affected if Users in the environment routinely open MODEL files from untrusted sources, making them potential targets for the malicious file parsing
A user is affected if their installed AutoCAD product version (including verticals) is less than 2022.1.6, 2023.1.7, 2024.1.7, or 2025.1.2 respectively, and they open untrusted MODEL files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2022.1.62023.1.72024.1.7
Do not open untrusted or unsolicited MODEL files in AutoCAD. Apply the vendor security update from Autodesk when available to patch the vulnerability.
2022.1.6, 2023.1.7, 2024.1.7, or 2025.1.2 (depending on product version)
- 1. Open Autodesk AutoCAD or affected product (Architecture, Electrical, Mechanical, MEP, Plant 3d, Civil 3d, or Advance Steel)
- 2. Check current version by typing 'VER' or 'ABOUT' in the command line
- 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. Download the appropriate update from Autodesk Account or Autodesk Desktop App
- 8. Install the update and restart the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1429 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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