TL;DR: 19 flaws in a Pepperl+Fuchs IO-Link master can turn one reachable management weakness into root access, including an authentication bypass and command-injection issues, according to Nozomi Networks Labs. OT gateways lose process trust when attackers can alter sensor visibility, actuator commands, or device keys.
Editorial analysis by NHI Mgmt Group, based on content published by Nozomi Networks: “Fooling the Master: Pepperl+Fuchs IO-Link Under Attack”.
By the numbers:
- Nozomi Networks Labs identified 19 vulnerabilities in the Pepperl+Fuchs IO-Link Master ICE2-8IOL-K45P-RJ45 running firmware version EtherNet/IP 1.7.3.
- The authentication bypass vulnerability, CVE-2026-27546, carries a CVSS v3.1 base score of 9.8.
- Multiple OS command injection issues, including CVE-2026-27547 through CVE-2026-27559, are rated 8.8 on CVSS v3.1.
Key questions
Q: Why do root-running command injection flaws matter more on OT bridge devices?
A: Because the command shell is not just touching a server process.
Q: What are the signs that an industrial device may be under active exploitation?
A: Look for unusual login attempts, crafted usernames, path traversal patterns, unexpected outbound connections, or sudden changes to host keys and device behaviour.
Q: What breaks when an industrial gateway's web login can be bypassed?
A: The access model breaks at the point where the interface assumes a verified identity before granting a session.
Practitioner guidance
- Isolate gateway management access Place the WebUI and SSH services on a dedicated management network with explicit allowlists for engineering workstations only.
- Validate device and server identity on maintenance paths Check SSH host keys on first use and monitor for unexpected key changes that could indicate impersonation.
- Remove unnecessary remote services Disable SSH, OPC UA, or MQTT on the device if they are not required for the operational process.
Bottom line: The core risk is not a single bug but a management surface that lets one network-reachable flaw become root access on an OT gateway.
Glossary terms: Industrial gateway, Authentication bypass, Command injection, Path Traversal
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Management-plane trust is the real failure mode here: the device's access model assumes that a web session equals a valid identity, but the bypass breaks that assumption before any role restriction can matter. In OT gateways, identity proofing, authorization, and root execution often converge in one interface, so a single logic flaw can invalidate the whole trust boundary. Practitioners should treat session creation and privilege assignment as a coupled control problem, not separate checks.
A question worth separating out:
Q: Should OT teams prioritise network segmentation or password hardening first for exposed gateways?
A: Prioritise segmentation first when a management interface is reachable from broader plant or corporate networks. Strong passwords still matter, but they do not stop an authentication bypass or file-read flaw from being exploited over the network. Segmentation narrows the reachable attack surface and buys time while firmware fixes are tested and deployed.
👉 Read our full editorial: IO-Link master flaws expose root control in OT networks