CVERadar

How to fix CVE-2026-110936: Siemens Software Center (exploited in the wild)

FIX GUIDE · EXPLOITED IN THE WILDCVE-2026-110936Siemens Software CenterHIGHCVSS 8.4cveradar.org

CVE-2026-110936 affects Siemens Software Center; exploited in the wild. What it is, who is affected, and the steps to fix and verify it.

What it is

A vulnerability has been identified in Siemens Software Center (All versions < V4.0.9.8). The affected application loads dynamic-link libraries (DLLs) from an uncontrolled search path. This could allow an authenticated local attacker to place a specially crafted DLL in a directory that the application searches, leading to arbitrary code execution with the privileges of the affected application.

  • Severity: HIGH (CVSS 4.0 8.4, vector CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N).
  • Weakness: CWE-427.
  • NVD published 2026-10-15, status Analyzed.

Who's affected

Anyone running Siemens Software Center in the version ranges below. Internet-facing instances are the priority.

  • siemens software center: up to (not including) 4.0.9.8.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

Exploitation status

Risk

  • EPSS (probability of exploitation activity in the next 30 days): 0.24%, higher than 14% of all scored CVEs (as of 2026-10-24).
  • CVERadar threat level: 57/100 (see methodology).
  • Likely ATT&CK techniques: T1574.001 DLL (inferred).

Remediation steps

  1. Find every instance. List where Siemens Software Center runs, including test, DR and forgotten internet-facing systems, and record the installed version.
  2. Upgrade to a fixed release. siemens software center: 4.0.9.8 or later. Get the build from the vendor advisory.
  3. If you can't patch today, follow CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  4. Verify the fix. Re-run the version check on every instance and confirm it reports the fixed build (4.0.9.8 or later). Re-scan from outside if the service is exposed.
  5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
  6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

  • Check the vendor advisory for indicators of compromise and review the affected system's logs back to the disclosure date.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

Sources

← Back to blog
Keep reading

Related articles

Track every exploited CVE

Full record for CVE-2026-110936, with the ATT&CK chain and every source. Browse what attackers are using right now, with fixes you can act on.

Exploited in the wildHow we score