Targets Siemens PLCs/web-server trace import allowing remote control of PLCs; risk to industrial operations and critical infrastructure across many organizations.
CVE-2026-63350
Imported trace files allow JavaScript execution that can control PLCs via web UI
Is CVE-2026-63350 being exploited?
Not confirmed. CVE-2026-63350 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-63350?
CVE-2026-63350 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63350?
Not known from our data. No patch reference has been recorded for CVE-2026-63350, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-63350 affect?
CVE-2026-63350 affects Siemens PLCs and web-server-enabled devices that accept imported trace files (requires 'Read diagnostics' privilege). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63350?
Restrict 'Read diagnostics', disable/validate trace imports, isolate affected devices, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Social-engineered import runs attacker JS in a user's browser (needs 'Read diagnostics'), allowing attacker to issue PLC operations within that user's rights.
Immediate action required
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
- affected< *
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.