Deception Check

DETECTION ENGINEERING / CVE-2026-110936

A valid signature
is not an all-clear.

Siemens Software Center: hunt the copy the attacker brought

CVE-2026-110936 is a patching task and an endpoint investigation. Attackers supplied their own signed Siemens executable, so checking your approved installations is only half the job.

The Siemens signature can be genuine. The code running inside the process can still be hostile.

That is the practical lesson from CVE-2026-110936. Siemens says attackers distributed an unchanged, signed copy of Software Center alongside malicious DLLs. The vulnerable program loaded those files when it started. Siemens also says it knows of no breach of its systems, products, or update channel. This is abuse of a legitimate executable, not evidence that Siemens shipped a compromised update. Siemens ProductCERT, October 19.

Do not stop the hunt at machines where your organization installed Siemens software. If the attacker brings the executable, your approved software inventory can miss the relevant copy entirely.

Why this is on the watch now

CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on October 20, 2026. The entry lists November 3 as the due date for covered federal agencies; that is not a grace period for everyone else. Siemens had already published its advisory on October 15 and confirmed exploitation on October 19. CISA's official catalog.

Before 4.0.9.8Affected Software Center versions
4.0.9.8 or laterVendor remediation
8.4 / HighSiemens CVSS v4.0 score

The flaw is an uncontrolled DLL search path, classified as CWE-427. Siemens' v4.0 vector specifies local access, high privileges, and no user interaction for the vulnerability. The ClickFix delivery campaign still involves persuading a user to act; delivery behavior and CVSS scoring describe different parts of the problem. SSA-580366.

Follow the code the process loaded

DLL side-loading exploits the relationship between an executable and a library it loads. A trusted application can become the host for an unexpected DLL; the executable's signature does not sign that DLL or establish that the process's behavior is safe. MITRE's DLL execution-hijacking guidance; Microsoft's code-signing guidance.

Reported pattern: ClickFix delivery leads to an attacker-supplied executable and DLL; the vulnerable signed program loads the DLL, and attacker code executes with its privileges. Each stage has a corresponding evidence check.
Reported pattern, illustrated by Deception Check. A genuine signature belongs to the executable, not to every file it loads. Siemens source.
Read the flow as text
  1. ClickFix deliveryA social-engineering lure leads the user to run attacker-provided content. Check: origin, download, and process records.
  2. The attacker brings the pairA bundle places a genuine Siemens executable beside a malicious DLL. Check: file origin, paths, hashes, and signatures separately.
  3. The signed program loads the DLLThe vulnerable application picks up the attacker's library. Check: actual module-load evidence, where available.
  4. Attacker code runsThe DLL executes with the application's privileges. Check: persistence, network activity, and response records.

Siemens associates the activity with the Romulus ClickFix campaign. Forescout describes Romulus as a delivery platform with multiple routes and payloads. Forescout reports LegionLoader on a separate route; that does not establish the payload in the Siemens case. Forescout Vedere Labs' investigation.

Keep the signature. Add the context.

Signature verification is useful evidence, not a reason to close an alert. Application control is not automatically defeated either: Microsoft's AppLocker supports a separate DLL rule collection. Check what your policy actually evaluates and enforces, and test changes in audit mode before enforcing them on operational workstations. Microsoft's DLL-rule documentation.

Two jobs, with different closure evidence

01 / PATCH MANAGEMENT

Verify the legitimate installation.

Confirm the approved copy is 4.0.9.8 or later. Siemens says existing installations update on startup; verify the resulting version rather than treating an update setting as proof. Use your managed deployment and change process.

Closure record: approved source, version, change record, and owner.

02 / INCIDENT INVESTIGATION

Explain the unexpected copy.

Find where it came from, what launched it, and which DLLs it loaded. Do not start a suspicious executable to make it update. Preserve the relevant records and use your incident-response process.

Closure record: evidence, scope, response, and unresolved gaps.

A software update can fix an approved installation. It does not remove every attacker-supplied copy, reverse earlier execution, or prove that persistence is gone.

A useful hunt starts with execution, not inventory

Search across endpoints for SiemensSoftwareCenter.exe, including hosts without an approved installation. Siemens calls out execution from AppData\Local\Programs started by msiexec, unexpected adjacent DLLs, and unplanned startup entries or scheduled tasks. Treat those as investigation leads and compare them with your deployment baseline. Vendor warning signs and indicators.

  1. Establish origin. Retain the installer or download record, executable path, hash, signer, user, and time. Was this an approved deployment, or an unexpected copy?
  2. Join the process to its modules. Use the endpoint's process identifier and time context to connect the launch with loaded-library records. Inspect the DLL's own path, hash, and signature. An adjacent file is not proof it was loaded.
  3. Look beyond the launch. Review startup changes, scheduled tasks, child processes, and network activity in the same timeline. A valid executable hash should not suppress that review.
  4. State the coverage. Record the hosts, retention window, and data sources searched. If module-load data was not collected, say so; an empty query cannot answer a question the telemetry never recorded.

Use the vendor's dated indicator list for a second search, not as your only detection. Its October 19 notice distinguishes active infrastructure from an already inactive distribution address. Historical contact can still matter after a server goes offline; refresh indicator status before applying blocks.

Prioritize consequence, not the vendor name

For OT teams, prioritize a suspect host according to the access it actually has. An engineering workstation with approved access to control systems warrants coordination with its operational owner. The Siemens name alone does not establish that the machine controls a plant, or that the campaign targeted industrial operations.

If isolation could interrupt an operational workflow, use the site's incident procedure and agree on a safe containment path. Keep evidence collection proportionate to urgency; do not let a perfect export delay necessary containment. Record who made the decision and what remains to investigate.

This is where we would spend the effort: a defensible chain from unexpected execution to an owned response. Deception can complement endpoint controls, but it is not a substitute for the process and module evidence needed to investigate this case.

Research notes

Reviewed October 20, 2026. This is analysis of vendor and primary-research reporting, not a Deception Check capture or a tested detection rule. No exploit samples were fetched or run. The flow illustrates the reported pattern; timestamps and sequence details must come from the endpoint being investigated.

Sources: Siemens advisory SSA-580366, v1.2; Siemens exploitation notice; CISA official KEV feed; Forescout's Romulus investigation; MITRE DLL technique; Microsoft AppLocker DLL rules. Corroborating national advisories: Bahrain NCSC, NCSC-TAD-2610-001 and Canadian Centre for Cyber Security, AV26-1063 (French).