CVE-2025-6973
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 · uneditedUse After Free vulnerability exists in the JT file reading procedure in SOLIDWORKS eDrawings on Release SOLIDWORKS Desktop 2025. This vulnerability could allow an attacker to execute arbitrary code while opening a specially crafted JT file.
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 confidenceUse After Free vulnerability in SOLIDWORKS eDrawings 2025's JT file parsing routine. When processing a specially crafted JT file, the application frees memory but continues to use a pointer to that freed memory region, potentially allowing an attacker to control reallocated memory and achieve arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm eDrawings 2025 installationOpen Windows Settings > Apps & Features or use 'Get-ItemProperty' in PowerShell to search for 'eDrawings' or check Program Files for SOLIDWORKS eDrawings folder. Verify the product name includes '2025'.Affected if SOLIDWORKS eDrawings 2025 is installed on the system
-
Identify installed eDrawings versionRight-click the eDrawings executable (typically in C:\Program Files\SOLIDWORKS\eDrawings or similar), select Properties, and check the File Version field under the Details tab. Alternatively, run 'Get-ItemProperty' on the .exe to retrieve the version.Affected if The version number shown corresponds to the 2025 release line and matches any affected version range for this CVE
-
Verify JT file handling capabilityLaunch eDrawings and attempt to open a JT file, or check if JT is listed in the supported file types under File > Open. Look for JT format in eDrawings options or file associations.Affected if JT file parsing is available and the user can open JT files within eDrawings 2025
-
Inspect recent JT file processing activityReview recent Windows Event Viewer logs under Application logs for eDrawings crash events, or check for any recent crash dumps involving eDrawings when opening JT files.Affected if eDrawings has recently processed JT files and exhibited unexpected behavior or crashes
If eDrawings 2025 is installed with the ability to open JT files, the environment is potentially affected by this Use After Free vulnerability when processing untrusted JT 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.
From vendor dataDo not open JT files from untrusted or unknown sources. Wait for and apply the vendor-provided security patch from SOLIDWORKS. Consider using application sandboxing or antivirus scanning as additional layers of defense.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6973 — 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-6973 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