# Siemens Software Center: exploited CVE and patch with deadline

> CVE-2026-110936 in Siemens Software Center is already being exploited by combining the signed installer with a malicious DLL. CISA sets a deadline of November 3.
> By José Maldonado · Cybersecurity · 2026-10-29

A legitimate installer signed by Siemens, with the house seal intact, plus a file called \`archive.dll\` placed alongside it. That is the combo attackers are using against [Siemens Software Center](https://threatfrontier.com/articles/siemens-software-center-cve-2026-110936-clickfix-dll-sideloading) according to the company itself, and which has ended with CVE-2026-110936 in CISA's catalog of exploited vulnerabilities on October 20. The federal deadline to patch expires on November 3, two weeks after inclusion on the list.

The vulnerability is a library search path problem, known as DLL sideloading. The application loads a library from a folder it does not control, and anyone who can leave a file there executes code with the program's privileges. CISA's note describes it as loading libraries from an uncontrolled path and acknowledges that an authenticated local attacker can take advantage of it, although in practice what has been seen is a social engineering campaign that pushes the victim to keep the good binary and the bad file together.

The fix is in version 4.0.9.8, and everything before the 4.0.9 branch is exposed. For a tool installed on engineering workstations, with access to technical documentation and in many cases to plant networks, the warning matters more than its score of 8.4 out of 10 on the CVSS v4 scale suggests. The damage does not depend on exploiting an exposed server, but on someone opening the wrong program on the wrong machine.

## An easy-to-exploit flaw

The mechanism can be understood with a simple analogy. The program needs a library and searches for it through a list of folders in order. If one of those folders can be written to by someone who should not, the program will load the first file it finds there, without checking who put it there.

In this case, the attacker places a malicious \`archive.dll\` next to an authentic copy of Software Center 3.5.8.7. The digital signature validates the executable, not the library it loads afterwards, and that is the gap. The legitimate binary serves as an alibi and the extra code runs with the same trust.

It is an old pattern that has come back strongly because it bypasses modern controls. An antivirus that trusts the executable's signature sees nothing unusual. Neither does a policy that allows installing software signed by the manufacturer. The result is an execution chain that looks authorized from start to finish.

## ClickFix, the social part of the attack

The campaign documented by the sector adds a layer of deception that does not even require an email attachment. The technique is called ClickFix and consists of convincing the victim to run a command to solve a problem that does not exist: a fake verification, a broken captcha, a connection error that does not actually occur.

The victim copies the command, pastes it into their terminal and with that installs the package of files that includes the signed Siemens binary and the malicious DLL. The campaign report mentions the use of a loader identified as Romulus to complete code execution.

What matters from a defensive standpoint is that the vector is not the vulnerability, but the combination of a local vulnerability with an instruction the user runs on their own.

That two-step process is what makes the technique so effective: there is no remote exploit to block with a firewall, only a person pasting a command they have been told is harmless.

## Why a November 3 deadline?

CISA added the CVE to the catalog of exploited vulnerabilities on October 20 and set November 3 as the deadline for federal agencies to apply the fix. It is the usual procedure since 2021: if there is confirmed exploitation, the deadline stops being theoretical and becomes an obligation with a date.

That calendar has a useful reading for the rest of organizations, which are not obliged but are interested. Fourteen days to update an internal tool is a reasonable margin if a software inventory exists. If it does not, the date becomes a race against a list of machines that nobody has.

For an industrial company the problem is greater. Software Center does not live on an isolated laptop, but on workstations that manage automation documentation and sometimes share a network with production systems. A local code executor in that environment is not an office breach.

## What you should check on your system

The first step is to know which version is installed. Everything before 4.0.9.8 requires an update, and in large installations it is advisable to check with an inventory rather than relying on the memory of the department that installed it.

The second step is to understand that the risk does not disappear with the patch if the campaign remains active. As long as machines with the old version exist, the technique still works, and those machines do not warn: the user perceives nothing unusual when the installer starts.

Action

Detail

Priority

Inventory versions

Everything before 4.0.9.8 is exposed

Immediate

Update to 4.0.9.8

Only fix published by the manufacturer

Immediate

Review unusual executions

Signed binary next to an unexpected DLL in the same folder

High

Train against ClickFix

No one should paste commands from a captcha or a verification

High

Isolate engineering stations

They should not share a flat network with plant systems

Media

A technical detail that helps detect the attack before it acts: if an \`archive.dll\` appears in the installation folder next to the Siemens executable, something has gone wrong. That combination is not part of the normal installation and is the most visible signature of this campaign.

## The lesson that keeps repeating

The pattern of attacking legitimate signed software has already surfaced this month on other fronts, and it is no coincidence. Attackers have understood that the trust control of modern systems lies in the signature and the vendor, not in the file's behavior. If the file comes from who it claims to come from, most defenses lower their guard.

The story of eMudhra's certificates in October showed the same logic from another angle: a certificate authority with weak keys casts doubt on the entire chain that depended on it, to the point of conditioning the exit of an entire distribution.

We covered it when detailing the [blow to eMudhra's TLS certificates](https://observatorioblockchain.com/en/cybersecurity/certificados-tls-emudhra-comprometidos/) and the Indian authority's subsequent decision to [abandon the global SSL business](https://observatorioblockchain.com/en/cybersecurity/emudhra-abandona-ssl-global/). In both cases, trust was placed in an object that claimed to be legitimate.

Signed software works the same way as certificates, with one important difference in the attacker's favor: here there is no need to break the cryptography or deceive an issuer. All it takes is for the victim to run a command and for the program to load the wrong library.

## What comes after the patch

Siemens has confirmed the exploitation and has published the fix, which is the most a manufacturer can do in this scenario. What remains in the customer's hands is the boring part: versions, inventory and training. The three fronts that usually fail.

If anything is clear from this case, it is that a vulnerability's score does not measure its real danger. An 8.4 with active exploitation and a deception vector that relies on the user is worth more, in practice, than a 9.8 with no campaign behind it. The November 3 date is not a formality: it is the last chance to patch before the technique is copied and stops being news.
