CVE-2026-3476 is a code injection vulnerability classified under CWE-94, affecting Dassault Systèmes SOLIDWORKS Desktop versions Release 2025 SP0 and Release 2026 SP0. The vulnerability arises from improper control over code generation when opening files, allowing an attacker to embed malicious code within a specially crafted SOLIDWORKS file. When a user opens such a file, the malicious code executes with the user's privileges, potentially leading to full system compromise. The CVSS 3.1 base score of 7.8 reflects a high severity, with attack vector local (AV:L), low attack complexity (AC:L), no privileges required (PR:N), but requiring user interaction (UI:R). The scope is unchanged (S:U), and the impact on confidentiality, integrity, and availability is high (C:H/I:H/A:H). Although no public exploits are known yet, the vulnerability poses a significant risk due to the widespread use of SOLIDWORKS in engineering and manufacturing industries. The flaw highlights the risks of processing untrusted files in complex desktop applications without sufficient input validation or sandboxing. Dassault Systèmes has not yet published patches, so users must rely on mitigations until updates are available.

The vulnerability allows attackers to execute arbitrary code on affected systems, potentially leading to complete compromise of the user's machine. This can result in theft of intellectual property, insertion of backdoors, disruption of engineering workflows, and loss of data integrity. Since SOLIDWORKS is widely used in product design and manufacturing, exploitation could have downstream effects on supply chains and critical infrastructure. The requirement for user interaction limits remote exploitation but does not eliminate risk, especially in environments where users frequently exchange design files. The high impact on confidentiality, integrity, and availability means organizations could face severe operational and reputational damage if exploited. Additionally, the lack of current patches increases exposure time, emphasizing the need for proactive defense.

1. Restrict SOLIDWORKS file sources to trusted and verified origins to reduce the risk of opening malicious files. 2. Implement application whitelisting and endpoint protection solutions that can detect and block suspicious code execution patterns related to SOLIDWORKS processes. 3. Educate users on the risks of opening unsolicited or unexpected SOLIDWORKS files, emphasizing verification before opening. 4. Use network segmentation to isolate engineering workstations from less secure network zones to limit lateral movement if compromise occurs. 5. Monitor system and application logs for unusual behavior indicative of code injection attempts. 6. Employ sandboxing or virtualized environments for opening untrusted SOLIDWORKS files when possible. 7. Stay alert for official patches or updates from Dassault Systèmes and apply them promptly once released. 8. Consider deploying file integrity monitoring on critical engineering workstations to detect unauthorized changes.