$30 IP-KVM Flaws Could Give Attackers BIOS-Level Control Across Enterprise Networks

Related

Ivanti Warns of New EPMM Flaw Exploited in Zero-Day Attacks

What happened Ivanti has disclosed a high-severity remote code execution...

Mirai-Based xlabs_v1 Botnet Exploits Android Debug Bridge to Hijack IoT Devices

What happened Hunt.io researchers have identified a new Mirai-derived botnet...

Cisco Releases Fix for DoS Flaw That Requires Manual Reboot to Recover

What happened Cisco has released security updates addressing a high-severity...

Palo Alto Networks Warns of Firewall RCE Zero-Day Exploited in Attacks

What happened Palo Alto Networks has disclosed a critical unpatched...

CISA Says ‘Copy Fail’ Flaw Now Exploited to Root Linux Systems

What happened CISA added CVE-2026-31431, a Linux kernel privilege escalation...

Share

What happened

Researchers at Eclypsium uncovered nine vulnerabilities across four low-cost IP-KVM devices from GL-iNet, Angeet/Yeeso, Sipeed, and JetKVM, flaws that could give attackers BIOS-level control over connected systems and bypass operating system security controls and EDR tools. The most severe issues affect the Angeet/Yeeso ES3 KVM, where an unauthenticated file upload flaw (CVE-2026-32297) can be chained with an OS command injection bug (CVE-2026-32298) to achieve pre-authentication remote code execution with root privileges. The researchers also found weak firmware verification, exposed debug interfaces, broken access controls, and insufficient rate limiting across the affected products, while internet scans identified more than 1,600 of these devices exposed online. 

Who is affected

Organizations using the affected IP-KVM devices in enterprise, lab, or remote management environments are affected, particularly those with devices exposed directly to the internet or deployed without segmented management networks. 

Why CISOs should care

Because IP-KVM devices operate below the host operating system, compromise can give attackers the equivalent of physical access to connected machines, enabling BIOS changes, boot manipulation, and control that remains invisible to host-based security tools. 

3 practical actions

  1. Isolate IP-KVM devices on dedicated management networks. Systems should be placed on separate VLANs and never exposed directly to the internet. 
  2. Restrict access with strong authentication and VPNs. Administrative access should be tightly controlled to reduce exposure of out-of-band management systems. 
  3. Inventory devices and apply firmware updates. Review environments for undocumented KVM devices and update affected products when vendor patches are available. 

For more coverage of newly disclosed security flaws, explore our reporting under the Vulnerabilities tag.

e1057c44fd23a2339dd83fc7bd88822e97b8b3544e012414c207939b16e0441d?s=150&d=mp&r=g
+ posts