CVE Intelligence
High

CVE-2026-59241 — A vulnerability has been identified in SIMATIC WinCC V7.5 (All versions), SIMATIC WinCC V8.0 (All...

A vulnerability has been identified in SIMATIC WinCC V7.5 (All versions), SIMATIC WinCC V8.0 (All versions < V8.0 Update 11), SIMATIC WinCC V8.1 (All versions < V8.1 Update 7). The affected application does not sufficiently restrict the permissions assigned to a database role. This could allow an authenticated remote attacker with database access to escalate privileges and execute arbitrary commands on the host system where SIMATIC WinCC is installed, potentially leading to a compromise of the system.

Published Oct 13, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: siemens

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.5% (30-day exploitation probability)+6
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.5%
ahead of 41% of scored CVEs · Oct 15, 2026
Affects
Siemens
SIMATIC WinCC V7.5 and 2 more
CVSS base
8.8
High · 3 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Siemens SIMATIC WinCC V7.5, Siemens SIMATIC WinCC V8.0, Siemens SIMATIC WinCC V8.1).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Siemens SIMATIC WinCC V7.5 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Siemens SIMATIC WinCC V8.0 < V8.0 Update 11 Vulnerable CVE Program (cve.org) e CISA ADP
Siemens SIMATIC WinCC V8.1 < V8.1 Update 7 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.7 CVSS 4.0 High — — productcert@siemens.com via NIST National Vulnerability Database
8.7 CVSS 4.0 High — — siemens via CVE Program (cve.org) e CISA ADP
8.8 CVSS 3.1 High 2.8 5.9 productcert@siemens.com via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.8 CVSS 3.1 High — — siemens via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: productcert@siemens.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-266

Other CVEs with this weakness →

EPSS over time FIRST

Oct 14, 2026 → Oct 15, 2026 · 2 reading(s) · max 0.50%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Deferred
    Oct 15, 2026 · NIST National Vulnerability Database
  • Affected products added · siemens/simatic wincc v7.5, siemens/simatic wincc v8.0, siemens/simatic wincc v8.1
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 13, 2026 · siemens

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

Elsewhere on this site

Siemens
every CVE for this vendor
CWE-266
other pages naming this weakness

Related CVEs (same products)

  • CVE-2025-30033 Uncontrolled Search Path Element in Siemens Automation License Manager V6.0 Aug 12, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-59241 is "A vulnerability has been identified in SIMATIC WinCC V7.5 (All versions), SIMATIC WinCC V8.0 (All...", rated High. It affects SIMATIC WinCC V7.5 (Siemens); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.50% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.