Siemens has issued a warning that a high-severity vulnerability, CVE-2026-110936, in its Siemens Software Center (SSC) is being actively exploited in the wild. The vulnerability is a DLL side-loading flaw with a CVSS v4.0 score of 8.4. Attackers associated with the "ClickFix" malware campaign are exploiting it by tricking users into running a malicious installer. This installer contains a legitimate, signed, but vulnerable version of the SSC client alongside a malicious DLL. When the legitimate application runs, it improperly loads the malicious DLL, leading to arbitrary code execution. Siemens has released version 4.0.9.8 to fix the issue and states that automatic updates should protect most users.
CVE-2026-110936The vulnerability exists because older versions of the Siemens Software Center client search for required DLLs in the same directory as the executable before searching in trusted system directories. An attacker can create a malicious installer package (e.g., AllMyBasic.msi) that places both a legitimate, signed Siemens.Software.Center.exe and a malicious DLL (e.g., a fake version.dll) in the same folder. When the user runs the executable, it loads the malicious DLL, granting the attacker code execution with the same privileges as the SSC client.
Siemens has clarified that the vulnerability is in the client application and not in their backend systems or product update channels. The attack relies on distributing a malicious package containing a vulnerable version of the software.
Siemens confirmed on October 19, 2026, that CVE-2026-110936 is being actively exploited. The attacks are attributed to the "ClickFix" malware campaign. This campaign uses social engineering to convince users to run malicious commands or installers, often bypassing traditional download scanners. The attackers bundle a legitimate but vulnerable version of SSC (specifically version 3.5.8.7 has been observed) into their malicious installers. Because the main executable is signed by Siemens, it may evade some security checks, making the attack more effective.
Successful exploitation allows an attacker to execute arbitrary code on the victim's machine with the permissions of the logged-in user running the SSC client. This can lead to the deployment of further malware, such as remote access trojans (RATs), spyware, or ransomware. The primary impact is a loss of confidentiality, integrity, and availability of the compromised system. Since the attack requires user interaction, the scale of impact depends on the success of the social engineering campaign. However, for organizations that use Siemens software extensively, a successful compromise could provide a foothold for attackers to move laterally within the network.
The following patterns may help identify vulnerable or compromised systems:
AllMyBasic.msiSiemens.Software.Center.exe%APPDATA%\Siemens\SoftwareCenter\D3-SA: Software Analysis (conceptual overlap).D3-PA: Process Analysis.AllMyBasic.msi or unexpected versions of Siemens.Software.Center.exe appearing on systems.D3-SU: Software Update.D3-EAL: Executable Allowlisting.The most direct mitigation is to apply the security update from Siemens, upgrading SSC to version 4.0.9.8 or later.
Mapped D3FEND Techniques:
Use application control solutions to prevent the execution of unauthorized installers and block the loading of untrusted DLLs.
Mapped D3FEND Techniques:
Ensure that application installation directories have proper permissions to prevent unprivileged users from writing malicious DLLs to them.
Mapped D3FEND Techniques:
Train users to be cautious about running installers from unverified sources, as this attack relies on social engineering.
Siemens initially discloses CVE-2026-110936.
Siemens releases version 4.0.9.8 of the Software Center to patch the vulnerability.
Siemens updates its advisory to confirm active exploitation in the wild.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.