dbcve.org
SolidworksApplication · 3ds

CVE-2026-3476

HIGH · 7.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 2026 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A Code Injection vulnerability affecting SOLIDWORKS Desktop from Release 2025 through Release 2026 could allow an attacker to execute arbitrary code on the user's machine while opening a specially crafted 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 confidence

A code injection vulnerability in SOLIDWORKS Desktop (versions 2025-2026) allows arbitrary code execution when users open specially crafted malicious files. The vulnerability stems from insufficient input validation during file parsing, enabling attackers to inject and execute arbitrary code on targeted machines.

MitigationUsers should avoid opening files from untrusted sources until vendor patches are applied. Organizations should implement file origin policies, application whitelisting, and deploy vendor security updates as soon as they become available.

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
SolidworksApplication
Affected:>= 2025, < 2026= 2026

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SOLIDWORKS Desktop is installed
    Open Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs. Look for entries containing 'SOLIDWORKS' or '3ds Solidworks'.
    Affected if SOLIDWORKS Desktop is present on the system
  2. Identify the installed SOLIDWORKS version
    Within the Programs and Features list, note the version number shown for SOLIDWORKS entries. Alternatively, check the installation directory for version information or right-click the SOLIDWORKS executable > Properties > Details to view the File Version.
    Affected if The displayed version matches 2025 or 2026 (any subversion)
  3. Confirm the version falls within affected ranges
    Compare your identified version to the affected ranges: version 2025 (any build) or exactly version 2026. Note that version 2025 with any patch level below 2026 is affected, and version 2026 is affected.
    Affected if The installed version is >= 2025 and < 2026, or equals exactly 2026
  4. Verify file parsing functionality is accessible
    Confirm the SOLIDWORKS application can open and parse CAD files. This is the default behavior for a standard installation. The vulnerability is triggered when the application opens specially crafted files.
    Affected if Users can open CAD files within SOLIDWORKS (standard functionality)
  5. Review current file origin policies
    Check if your organization or system has application whitelisting enabled or file origin restrictions configured. This is informational to understand the attack surface, as the vulnerability can be triggered when a user opens a malicious file.
    Affected if No file origin restrictions or application whitelisting is enforced, allowing users to open files from untrusted sources

If the installed SOLIDWORKS version is 2025 through 2026 and the application can parse files (standard behavior), the environment is vulnerable to code injection through malicious files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026 or later
Fixed in 2026
Interim mitigation

Users should avoid opening files from untrusted sources until vendor patches are applied. Organizations should implement file origin policies, application whitelisting, and deploy vendor security updates as soon as they become available.

Recommended fix Moderate confidence

SOLIDWORKS 2027 or later

  1. 1. Verify the current installed SOLIDWORKS Desktop version by opening SOLIDWORKS and navigating to Help > About SOLIDWORKS
  2. 2. Download SOLIDWORKS 2027 or later from the official 3DS.com customer portal (https://www.3ds.com/solidworks)
  3. 3. Ensure all dependent applications and plugins are compatible with the new version before upgrading
  4. 4. Perform a full backup of existing SOLIDWORKS files, templates, and settings
  5. 5. Uninstall the current SOLIDWORKS version through Windows Control Panel > Programs and Features
  6. 6. Run the installer for SOLIDWORKS 2027 or later with administrator privileges
  7. 7. Activate the license using your existing serial number or transfer to a new license if required
  8. 8. Test critical workflows and custom templates to verify functionality after upgrade
Caveat Potential compatibility issues with existing custom macros, templates, or third-party add-ins may require updates or reconfiguration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solidworks Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3476 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3476 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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