CVE-2025-5047
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 DGN 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 confidenceAn uninitialized variable vulnerability exists in Autodesk AutoCAD's DGN file parser. When a specially crafted malicious DGN file is opened, it triggers the uninitialized variable condition, which can be exploited for denial of service (crash), information disclosure (reading sensitive memory contents), or arbitrary code execution within the current process context.
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= 2026= 2026= 2026= 2026= 2026= 2026= 2026= 2026CVSS 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 Autodesk productOpen the application and go to Help > About AutoCAD, or check Add/Remove Programs to see which Autodesk product is installedAffected if Any of the following products are installed: Advance Steel, AutoCAD, AutoCAD Architecture, AutoCAD Electrical, AutoCAD LT, AutoCAD Map 3D, AutoCAD Mechanical, or AutoCAD MEP version 2026
-
Verify the product version numberCheck the product version through the application's About dialog or by running the application's version check from the command lineAffected if The installed version is exactly 2026
-
Confirm DGN file support is enabledCheck whether DGN import/export or DGN preview functionality is active by examining the product's file association settings or plugin configurationAffected if DGN file handling or preview capabilities are enabled in the product settings
-
Inspect DGN file preview handlersExamine the system configuration to determine if DGN preview handlers are registered and active for the file explorer or the Autodesk productAffected if DGN preview handlers are enabled at the system or application level
If any of the listed Autodesk products (Advance Steel, AutoCAD, or its vertical variants) version 2026 is installed with DGN file handling enabled, the environment is potentially affected by CVE-2025-5047.
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.
From vendor dataApply the vendor patch from Autodesk when available. Until then, implement defense-in-depth by restricting DGN file sources, disabling DGN file preview handlers, and running AutoCAD in isolated environments or sandboxes to limit the impact of successful exploitation.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5047 — 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-5047 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