CVE-2019-5186 is a stack buffer overflow in the I/O-Check service (iocheckd) of WAGO controllers. When a packet triggers parsing of a crafted XML cache file, an overlong interface element name is written with sprintf() into a fixed stack buffer for the config_interfaces command. NVD scores it 7.0; it needs a login.
Vulnerability summary
CVSS base score
7
High severity
EPSS score (FIRST)
0.8%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2019-5186 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| WAGO PFC200 (750-82xx/xxx-xxx), iocheckd I/O-Check service | cpe:2.3:o:wago:pfc200_firmware:03.02.02\(14\):*:*:*:*:*:*:* | Firmware before FW16 (CERT@VDE VDE-2020-011, which names the FW16 release as the fix target). NVD lists only firmware 03.02.02(14) |
| WAGO PFC100 (750-81xx/xxx-xxx), iocheckd I/O-Check service | — | Firmware before FW16 (CERT@VDE VDE-2020-011). Not in NVD's CPE list |
| WAGO 762-4xxx, 762-5xxx and 762-6xxx, iocheckd I/O-Check service | — | Firmware before FW16 (CERT@VDE VDE-2020-011). Not in NVD's CPE list |
What does this mean for affected devices?
NVD carries the Cisco Talos description, which names the code path: "At 0x1eb9c the extracted interface element name from the xml file is used as an argument to /etc/config-tools/config_interfaces interface=CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) with CWE-120 and CWE-787; Cisco Talos, the CNA, published the record on 2020-03-23 and NVD links it to Talos report TALOS-2019-0966 (NVD, CVE record).
How does it relate to CVE-2019-5166?
Both come from the same parser. iocheckd reads an XML cache file from the device and builds config-tools command lines from its elements with sprintf(). CVE-2019-5166 is the generic overflow in that cache parsing; CVE-2019-5186 is the specific case of the interface element. VDE-2020-011 lists 20 such CVEs from Cisco Talos, several of them for other elements of the same file. The attack complexity is high in the NVD and CERT@VDE vector (AC:H), so the score is 7.0 rather than 7.8.
Which devices and firmware are affected?
WAGO's advisory VDE-2020-011 covers 20 iocheckd flaws reported by Cisco Talos, CVE-2019-5186 among them. It lists PFC100 (750-81xx/xxx-xxx), PFC200 (750-82xx/xxx-xxx) and the 762-4xxx, 762-5xxx and 762-6xxx devices with firmware before FW16 as affected, and names the FW16 release, dated Q2/2020 in the advisory, as the fix target. NVD's CPE lists only PFC200 firmware 03.02.02(14), the build Talos tested, so PFC100 and the 762 devices do not show up in an NVD-only scan. The advisory's summary sets the precondition: "An attacker needs an authorized login on the device in order to exploit the herein mentioned vulnerabilities", and the attacker must be "able to create files on the device".
What should operators do?
Disable the I/O-Check service after commissioning, update to FW16 or later, restrict network access and keep the controller off the internet. Limit who holds a login on the device, since writing the cache file needs one. The unauthenticated I/O-Check overflows from 2019, such as CVE-2019-5075 and CVE-2019-5082, show why the service should not stay reachable at all. See the WAGO PFC controller guide and the memory corruption fix guide.
CVE-2019-5186 is not in the CISA KEV catalog as of 2026-11-22 (catalog version 2026.11.20, 1,790 entries). FIRST EPSS gives it 0.00846, the 59th percentile, in the 2026-11-21 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD (read 2026-11-22): status Modified; published 2020-03-23; NVD Primary CVSS v3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, v2 4.4; CWE-120 and CWE-787 (NVD); CPE pfc200_firmware 03.02.02(14); reference TALOS-2019-0966; description names sprintf() at 0x1eb9c into sp+0x40, strcpy() at 0x1ea08, crash at interface length 0x3c4. — NVD
- CERT@VDE VDE-2020-011 (initial release 2020-03-09, revision 2 2025-05-22), HTML and CSAF read 2026-11-22: affects 750-81xx/xxx-xxx (PFC100), 750-82xx/xxx-xxx (PFC200), 762-4xxx, 762-5xxx, 762-6xxx with firmware <FW16; CVE-2019-5186 CVSS v3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-120; attacker needs an authorized login and must be able to create files on the device; mitigation: disable I/O-Check service, restrict network access, no direct internet connection, disable unused ports; remediation text: the vulnerabilities are expected to be fixed in FW16 Release in Q2/2020; 20 CVEs listed (CVE-2019-5166 to CVE-2019-5186 except CVE-2019-5183); reported by Kelly Leuschner of Cisco Talos. — CERT@VDE VDE-2020-011
- CVE record (checked 2026-11-22): state PUBLISHED, CNA Cisco Talos (talos), published 2020-03-23; problem type "stack buffer"; affected WAGO PFC200 Firmware version 03.02.02(14); no CNA CVSS score in the record. — CVE.org
- Not in the CISA KEV catalog, catalog version 2026.11.20, 1,790 entries, checked 2026-11-22. — CISA KEV
- EPSS 0.00846, percentile 0.58958, dataset 2026-11-21, read 2026-11-22. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Does CVE-2019-5186 need authentication?
Yes. CERT@VDE VDE-2020-011 says an attacker needs an authorized login on the device and must be able to create files on it; the crafted XML cache file is parsed when a packet triggers it.
Which WAGO firmware fixes it?
VDE-2020-011 lists firmware before FW16 as affected and names the FW16 release (Q2/2020) as the fix target. Its first recommendation is to disable the I/O-Check service after commissioning.
What exactly overflows?
The stack buffer at sp+0x40 that holds the /etc/config-tools/config_interfaces command line. Interface names longer than 512 minus the command prefix overflow it, and an interface value of length 0x3c4 crashes the service (NVD description).
Why is the score 7.0 and not 7.8?
NVD and CERT@VDE both use attack complexity High (AC:H) for CVE-2019-5186, which gives CVSS v3.1 7.0. The related CVE-2019-5166 uses AC:L and scores 7.8.
Is CVE-2019-5186 in the CISA KEV catalog?
No, not as of 2026-11-22 (catalog version 2026.11.20, 1,790 entries). FIRST EPSS rates it 0.00846 (59th percentile) in the 2026-11-21 dataset.
Questions about this page?