Join our Newsletter — 33% off our NHI Course

IO-Link master compromise: what OT and IAM teams should notice

 

(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 19129
Topic starter  

TL;DR: 19 vulnerabilities were found in a Pepperl+Fuchs IO-Link master, including an authentication bypass that yields an Admin session and command-injection flaws that can hand attackers root control of the device, according to Nozomi Networks Labs. In OT environments, management-plane trust collapses into process risk when a bridge device can alter sensor data and actuator commands.

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: 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.

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.

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.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →



   
Quote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.