CVE-2018-16561 is a denial-of-service flaw in Siemens SIMATIC S7-300 CPUs: one crafted S7 communication packet, sent over Ethernet, PROFIBUS or MPI, puts the CPU into DEFECT mode, where it stays until someone restarts it by hand. NVD and Siemens both score it 7.5. Siemens fixes it in S7-300 firmware V3.X.16.
Vulnerability summary
CVSS base score
7.5
High severity
EPSS score (FIRST)
1.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2018-16561 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Siemens SIMATIC S7-300 CPU family (incl. related ET200 CPUs and SIPLUS variants) | cpe:2.3:o:siemens:simatic_s7-300_firmware:-:*:*:*:*:*:*:* | All versions before V3.X.16; fixed in V3.X.16 (Siemens SSA-306710). NVD CPE has no version |
| Siemens SIMATIC S7-300F, S7-300FS and S7-300T CPUs | cpe:2.3:o:siemens:simatic_s7-300f_firmware:-:*:*:*:*:*:*:* | Listed in NVD's CPE configuration without a version; Siemens SSA-306710 covers them as part of the S7-300 CPU family, fixed in V3.X.16 |
What does this mean for affected devices?
NVD carries the Siemens description: "The affected CPUs improperly validate S7 communication packets which could cause a Denial-of-Service condition of the CPU. The CPU will remain in DEFECT mode until manual restart." NVD's Primary score is CVSS v3.0 7.5 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), with NVD-CWE-noinfo as its own weakness entry; Siemens classes it CWE-20 (improper input validation). The record was published on 2019-04-17 (NVD, CVE record).
Which interfaces can carry the attack?
Siemens ProductCERT SSA-306710 (V1.1, 2020-02-10) says exploitation needs "a specially crafted S7 communication packet to a communication interface of the CPU. This includes Ethernet, PROFIBUS, and Multi Point Interfaces (MPI)." No privileges or user interaction are required. That is what sets this CVE apart: a PROFIBUS or MPI segment is not a safe zone, because the packet does not have to arrive over Ethernet. The CPU stops its core function and stays in DEFECT mode until a manual restart.
How severe is it?
Siemens scores it CVSS v3.1 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C) and NVD agrees on 7.5 with a v3.0 vector. The impact is availability only, but a stopped CPU means a stopped process until someone on site restarts it. At publication Siemens knew of no public exploitation. Siemens credits the China Industrial Control Systems Cyber Emergency Response Team (CIC) for coordinated disclosure, and CISA republished it as ICSA-19-043-04.
How do you fix or mitigate it?
| Product (Siemens wording) | Affected | Fixed |
|---|---|---|
| SIMATIC S7-300 CPU family (incl. related ET200 CPUs and SIPLUS variants) | before V3.X.16 | V3.X.16 or later |
The "X" stands for the CPU-specific part of the firmware number. NVD's CPE lists S7-300, S7-300F, S7-300FS and S7-300T firmware with no version, so it cannot tell a patched CPU from an unpatched one. Siemens' only specific mitigation is to operate the devices within trusted networks, plus its general advice to protect network access. In practice that means controlling who can connect to the CPU's Ethernet port and who can plug into the PROFIBUS or MPI line.
Our PROFIBUS protocol security guide lists this advisory among the S7-300 flaws reachable over PROFIBUS, and the S7comm protocol security guide covers the S7 protocol. Other S7-300 denial-of-service pages are CVE-2016-3949 and the PROFINET DCP flaws CVE-2017-2680 and CVE-2017-2681, fixed for the S7-300 in V3.X.14.
CVE-2018-16561 is not in the CISA KEV catalog as of 2026-11-20 (catalog version 2026.11.18, 1,786 entries). FIRST EPSS gives it 0.01396, the 73.0th percentile, in the 2026-11-19 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD (read 2026-11-20): status Modified; published 2019-04-17; NVD Primary CVSS v3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, v2 7.8; CWE NVD-CWE-noinfo (NVD), CWE-20 (secondary); CPE S7-300, S7-300F, S7-300FS, S7-300T firmware without version; reference SSA-306710. — NVD
- Siemens SSA-306710 V1.1 (published 2019-01-08, updated 2020-02-10), read 2026-11-20: S7-300 CPU family (incl. related ET200 CPUs and SIPLUS variants) all versions before V3.X.16, update to V3.X.16; crafted S7 packet via Ethernet, PROFIBUS or MPI causes DEFECT mode until manual restart; CVSS v3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C; CWE-20; mitigation: operate only within trusted networks; no public exploitation known at publication; credits CIC. — Siemens ProductCERT SSA-306710
- CISA ICSA-19-043-04 CSAF (Siemens SIMATIC S7-300 CPU, version 2, current release 2020-02-10), read 2026-11-20: CVE-2018-16561, CWE-20, CVSS v3.1 7.5. — CISA CSAF ICSA-19-043-04
- CVE record (checked 2026-11-20): state PUBLISHED, CNA Siemens, published 2019-04-17; problem type improper input validation; affected SIMATIC S7-300 CPUs all versions before V3.X.16. — CVE.org
- Not in the CISA KEV catalog, version 2026.11.18 (1,786 entries, released 2026-11-18), checked 2026-11-20. — CISA KEV
- EPSS 0.01396, percentile 0.72995, dataset 2026-11-19, read 2026-11-20. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which firmware fixes CVE-2018-16561?
S7-300 CPU firmware V3.X.16 or later, where X is the CPU-specific part of the version number. Siemens SSA-306710 applies this to the whole S7-300 CPU family, including related ET200 CPUs and SIPLUS variants.
Can the attack come over PROFIBUS or MPI?
Yes. Siemens SSA-306710 names Ethernet, PROFIBUS and Multi Point Interfaces (MPI) as interfaces that can carry the crafted S7 packet, so anyone with access to the fieldbus or an MPI adapter can trigger it, not only hosts on the plant network.
Does the CPU recover on its own?
No. The affected CPU stays in DEFECT mode until a manual restart, according to Siemens SSA-306710 and the CVE description, so the controlled process stays down until someone intervenes on site.
What can I do if I cannot update the S7-300?
Siemens recommends operating the devices only within trusted networks and protecting network access. Restrict which hosts can reach the CPU over Ethernet, and control physical access to PROFIBUS and MPI connectors and programming adapters.
Questions about this page?