External risk intelligence

Metz Connect EWIO2 Root Credentials Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-41733

The affected IoT gateways and automation controllers feature a network-accessible commissioning interface. These devices are frequently deployed in environments requiring remote management, making internet-facing exposure a common and expected configuration pattern for this class of hardware.

Metz Connect Ewio2 M Firmware

before 2.2.0

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in certain devices that allows unauthenticated attackers to remotely set administrative credentials, potentially leading to unauthorized control and access. The issue stems from a flaw in the device's setup process that fails to verify if the device has already been initialized. This could allow an attacker to gain full administrative privileges without needing any prior access or authentication.

  • Unauthenticated remote access to set device administrator.
  • Critical control access if exploited remotely.
  • Confirm relevance and verify device initialization status.

Attack Path

How an attacker could exploit the issue

An attacker could target the device's commissioning wizard over the network without needing any credentials. By sending specially crafted POST requests, they can bypass the wizard's checks and establish their own root credentials, effectively taking control of the device. This vulnerability could lead to a complete compromise of the device's functionality and data.

  • No authentication required.
  • Attacker sets root credentials.
  • Full device control possible.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an unauthenticated remote attacker could bypass initialization checks and set root credentials on affected devices. This could lead to unauthorized control over the device and its connected systems.

  • Device configuration and control.
  • Network-based credential setting.
  • Compromised system integrity.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world ownership for this vulnerability likely falls to the teams managing IoT infrastructure and operational technology (OT) environments. Because the vulnerability allows unauthenticated remote attackers to set root credentials, identifying all deployed instances of the affected devices is the critical first step. This discovery process must prioritize confirming reachability and business criticality, then identifying the accountable owner for each instance to plan a targeted remediation strategy.

  • Identify affected device deployments.
  • Verify network exposure and criticality.
  • Plan remediation with device owners.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Metz Connect EWIO2?

The EWIO2 is a series of IoT gateways and automation controllers used to manage and interface with building automation systems. These devices act as communication hubs that connect various field-level sensors and actuators to larger management networks, enabling centralized control and monitoring of facility infrastructure.

What is the weakness in CVE-2025-41733?

This vulnerability is classified as CWE-305: Authentication Required, which generally concerns the failure to properly enforce authentication. In this specific case, the device's commissioning wizard fails to check if a device has already been initialized, allowing an unauthenticated user to interact with setup functions that should be locked once a system is configured.

How can an attacker trigger this vulnerability?

An attacker triggers this by sending unauthorized POST requests to the device's commissioning wizard over the network. It is important to note that this flaw specifically targets the device's setup logic; if a device is not in a state where the commissioning wizard is receptive or if the network path to that specific interface is blocked, the attack cannot be successfully initiated.

Who should be concerned about this vulnerability?

Anyone managing these controllers in network-connected environments should be concerned. According to Halo Surface Signal, these devices are often deployed in configurations requiring remote management, making internet-facing exposure common. If your EWIO2 units are accessible from outside your local network, they are at significantly higher risk.

What should I do if I use these devices?

Your first step is to locate all deployed EWIO2 instances within your infrastructure and confirm their current network exposure. Prioritize identifying which units are reachable from external networks and determine the business criticality of those systems. Once identified, work with the device owners to plan for the application of official firmware updates.

References