DGN File Parsing Uninitialized Variable Vulnerability
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A 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.
- Published
- Aug 15, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-457
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · autodesk
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| autodesk | advance steel | cpe:2.3:a:autodesk:advance_steel |
| autodesk | autocad | cpe:2.3:a:autodesk:autocad |
| autodesk | autocad architecture | cpe:2.3:a:autodesk:autocad_architecture |
| autodesk | autocad electrical | cpe:2.3:a:autodesk:autocad_electrical |
| autodesk | autocad lt | cpe:2.3:a:autodesk:autocad_lt |
| autodesk | autocad map 3d | cpe:2.3:a:autodesk:autocad_map_3d |
| autodesk | autocad mechanical | cpe:2.3:a:autodesk:autocad_mechanical |
| autodesk | autocad mep | cpe:2.3:a:autodesk:autocad_mep |
| autodesk | autocad plant 3d | cpe:2.3:a:autodesk:autocad_plant_3d |
| autodesk | civil 3d | cpe:2.3:a:autodesk:civil_3d |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- autodesk advance steel2026
- autodesk autocad2026
- autodesk autocad architecture2026
- autodesk autocad electrical2026
- autodesk autocad lt2026
- autodesk autocad map 3d2026
- autodesk autocad mechanical2026
- autodesk autocad mep2026
- autodesk autocad plant 3d2026
- autodesk civil 3d2026
Versions reported by the vendor
Affected version ranges reported by the assigning authority (autodesk). Independent of NVD's CPE analysis and usually ahead of it.
Autodesk Advance Steel
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Autodesk AutoCAD
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Autodesk AutoCAD Architecture
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Autodesk AutoCAD Electrical
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Autodesk AutoCAD LT
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Autodesk AutoCAD MAP 3D
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Autodesk AutoCAD Mechanical
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Autodesk AutoCAD MEP
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Autodesk AutoCAD Plant 3D
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Autodesk Civil 3D
- 2026 and later · before 2026.1affected
- 2025 and later · before 2025.1.3affected
- 2024 and later · before 2024.1.8affected
- 2023 and later · before 2023.1.8affected
Same product
autodesk: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-40159An Information Disclosure vulnerability for JT files in Autodesk Inventor 2022, 2021, 2020, 2019 in conjunction with other vulnerabilities m32Monitor
- CVE-2021-40158A maliciously crafted JT file in Autodesk Inventor 2022, 2021, 2020, 2019 and AutoCAD 2022 may be forced to read beyond allocated boundaries32Monitor
- CVE-2021-27042A maliciously crafted DWG file can be used to write beyond the allocated buffer while parsing DWG files.32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-1276Apr 15, 2025 · DWG File Parsing Out-of-Bounds Write Vulnerability31Monitor
- ← EarlierCVE-2025-5046Aug 15, 2025 · DGN File Parsing Out-of-Bounds Read Vulnerability31Monitor
- Later →CVE-2025-5048Aug 15, 2025 · DGN File Parsing Memory Corruption Vulnerability31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-457 · Use of Uninitialized VariableCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.