CVE-2025-1276
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 DWG file, when parsed through certain Autodesk applications, can force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, 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 confidenceAn out-of-bounds write vulnerability exists in certain Autodesk applications when parsing maliciously crafted DWG files. The vulnerability occurs during DWG file parsing, allowing a malicious actor to write data beyond allocated memory boundaries, potentially leading to code execution, crash, or data corruption.
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>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 2023, < 2023.1.7>= 2024, < 2024.1.7>= 2025, < 2025.1.2>= 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 installed Autodesk productOpen Windows Settings > Apps & Features or use 'Get-ItemProperty' in PowerShell to list installed programs containing 'Autodesk' or the specific product names (Advance Steel, AutoCAD, AutoCAD Architecture, etc.)Affected if Any of the affected products from the list is installed
-
Find the installed version numberRight-click the application shortcut, select Properties, and view the 'Details' tab for the product version, or run 'Get-ItemProperty' on the executable path to retrieve the FileVersionAffected if Version cannot be determined or does not match the product's typical versioning scheme
-
Compare version against affected rangesCheck if the installed version falls within any of these ranges: 2023.x (before 2023.1.7), 2024.x (before 2024.1.7), or 2025.x (before 2025.1.2)Affected if The installed version is 2023.1.7 or higher, 2024.1.7 or higher, or 2025.1.2 or higher - these are patched versions
-
Verify DWG file parsing capabilityConfirm the installed product supports DWG file operations - all listed products (AutoCAD, Advance Steel, AutoCAD Architecture/Electrical/LT/Map 3D/Mechanical/MEP) can open and parse DWG files by defaultAffected if The product can open DWG files (which is the default behavior for all listed applications)
You are affected if you have any of the listed Autodesk products installed with version 2023.x before 2023.1.7, 2024.x before 2024.1.7, or 2025.x before 2025.1.2, and the application can process DWG files (which is the default functionality).
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 · scoped2023.1.72024.1.72025.1.2
Avoid opening DWG files from untrusted or unknown sources. Apply vendor patches for affected Autodesk products once available.
AutoCAD 2023.1.7 or later; 2024.1.7 or later; 2025.1.2 or later (depending on your product version)
- Identify the specific Autodesk product and version (2023, 2024, or 2025) currently installed
- For AutoCAD 2023 and verticals: Upgrade to version 2023.1.7 or later
- For AutoCAD 2024 and verticals: Upgrade to version 2024.1.7 or later
- For AutoCAD 2025 and verticals: Upgrade to version 2025.1.2 or later
- Download the update from the Autodesk Account portal or use the Autodesk Desktop App to install the update
- Restart the application after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
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 locallyCheck whether your project pulls in CVE-2025-1276 — 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-1276 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