Skip to main content

Solidworks Desktop EUVDEUVD-2026-12419

| CVE-2026-3476 HIGH
Code Injection (CWE-94)
2026-03-16 3DS
7.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious SOLIDWORKS file
  2. Exploit
    User opens file in SOLIDWORKS Desktop
  3. Execution
    Code injection payload executed
  4. Impact
    Arbitrary code runs with user privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

SOLIDWORKS Desktop Release 2025 or 2026 installed and configured to open crafted file formats. User interaction required: victim must open the malicious file. No authentication bypass needed.

Impact

The CVSS 7.8 score indicates high severity, but real-world risk is moderated by several factors. The local attack vector (AV:L) and required user interaction (UI:R) significantly limit exploitation scalability compared to remote vulnerabilities. With no privileges required (PR:N) and low attack complexity (AC:L), successful exploitation is straightforward once a user is tricked into opening a malicious file. The absence of KEV listing indicates no known active exploitation, and without EPSS data or public POCs, the immediate threat level appears theoretical rather than imminent. This represents a priority for organizations using SOLIDWORKS but not an emergency compared to actively exploited vulnerabilities.

Exploit ScenarioDerived

An attacker crafts a malicious SOLIDWORKS file containing embedded code and distributes it via email phishing or compromised file sharing platforms targeting engineering firms. When an unsuspecting engineer opens the file in SOLIDWORKS Desktop 2025 or 2026, the embedded code executes with the user's privileges, potentially installing malware, exfiltrating sensitive CAD designs, or establishing persistence for further attacks. The attack requires convincing social engineering since direct user action is needed to open the file.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 16, 2026

A code injection vulnerability in SOLIDWORKS Desktop releases 2025 through 2026 allows attackers to execute arbitrary code on victim machines by tricking users into opening specially crafted files. The vulnerability requires local access and user interaction but provides complete system compromise with high impact to confidentiality, integrity, and availability (CVSS 7.8). No evidence of active exploitation or proof-of-concept code has been reported.

RemediationAI

Users should immediately check the 3DS security advisory at https://www.3ds.com/trust-center/security/security-advisories/CVE-2026-3476 for patch availability and upgrade instructions for SOLIDWORKS Desktop. Until patches are applied, implement compensating controls including restricting SOLIDWORKS file sources to trusted origins only, scanning files with updated antivirus before opening, and educating users about the risks of opening SOLIDWORKS files from untrusted sources or unexpected emails. Consider implementing application sandboxing or virtualization for high-risk users who must work with external files.

Affected VersionsENISA

SOLIDWORKS Desktop Release 2025 SP0 ≤Release 2025 SP5
SOLIDWORKS Desktop Release 2026 SP0

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability affects Dassault Systèmes SOLIDWORKS Desktop software (CPE: cpe:2.3:a:dassault_systèmes:solidworks_desktop:*:*:*:*:*:*:*:*), a professional 3D CAD application widely used in engineering and manufacturing. The root cause is improper input validation leading to code injection (CWE-94), where the application fails to properly sanitize or validate data within specially crafted files before processing them. This allows malicious code embedded in the file to be interpreted and executed by the application with the privileges of the current user.

Know when Solidworks Desktop gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

A Code Injection vulnerability affecting in 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.

Executive ViewAI

Why It Matters

A high-severity code injection vulnerability in SOLIDWORKS Desktop (versions 2025-2026) could allow attackers to execute arbitrary code on affected systems through maliciously crafted files, potentially compromising sensitive CAD designs, intellectual property, and system integrity. Organizations using SOLIDWS for product design or engineering work face immediate risk of data theft and operational disruption, with no patch currently available to remediate the threat.

Business Impact: High
Compensating Controls

Disable or restrict SOLIDWORKS Desktop file import functionality where possible; implement application whitelisting to prevent unauthorized code execution; enforce network segmentation isolating SOLIDWORKS workstations from sensitive data repositories; require email gateway scanning and user training to reject suspicious CAD file attachments; enable enhanced logging and EDR monitoring on affected systems to detect exploitation attempts; consider temporary migration of non-critical design work to offline or air-gapped systems until patch is released.

Threat Intelligence Overview

EPSS Score
0.0%
Top 94% exploitable
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy