External risk intelligence

OpenRemote Core Authentication Bypass via MQTT Device Impersonation.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-134287

The vulnerability affects an MQTT handler within the OpenRemote core, which is typically used for IoT device management and communication. While MQTT brokers can be exposed to the internet, they are frequently deployed within isolated internal networks or behind VPNs to manage local device fleets, making public-facing exposure possible but not a standard design pattern for all deployments.

Authentication Bypass

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in OpenRemote's core systems that could allow unauthorized access to device information and control. It impacts how devices are authenticated within the system, potentially enabling attackers to impersonate legitimate devices to read or modify assets. The main concern is confirming relevance and exposure within your specific deployment.

  • Unauthenticated attackers can impersonate devices.
  • Impacts IoT device management and communication.
  • Confirm relevance and exposure for your systems.

Attack Path

How an attacker could exploit the issue

An attacker can bypass authentication by publishing a known device's public certificate to a specific topic. This allows them to impersonate a legitimate device connected via MQTT, enabling them to access and modify assets managed by the OpenRemote core.

  • Unauthenticated network access required.
  • Publish known device certificate to topic.
  • Impersonate devices; read/modify assets.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated attackers to impersonate provisioned devices, potentially enabling them to read or modify assets associated with those devices. This may occur when an attacker publishes a known device's public certificate to a provisioning request topic.

  • Device service account credentials.
  • Publishing a known device certificate.
  • Unauthorized asset modification or access.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in OpenRemote core's MQTT provisioning handler requires immediate attention from teams managing IoT device onboarding and communication. The first practical step is to identify all instances of the affected OpenRemote core, determine their network exposure and business criticality, and confirm the responsible system owner for triage and remediation planning.

  • Identify affected OpenRemote instances.
  • Verify network exposure and criticality.
  • Plan remediation with accountable 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 OpenRemote core?

OpenRemote core is an IoT platform used for managing, connecting, and controlling diverse device fleets. It facilitates communication between hardware and centralized management systems, often handling data ingestion and asset provisioning through protocols like MQTT.

How does CVE-2026-134287 work?

This vulnerability is an authentication bypass, classified under CWE-287. It occurs because the system fails to verify that a device actually possesses its private key during the provisioning process. Instead, it accepts a publicly known device certificate as sufficient proof of identity, allowing an attacker to impersonate that device.

What must an attacker do to trigger this flaw?

An attacker needs network access to the MQTT broker. They must publish a known device's public certificate to the specific provisioning request topic handled by the software. Simply connecting to the network without sending this specific certificate to the correct topic does not trigger the bypass.

Do I need to worry if my system is internal?

According to Halo Surface Signal, this vulnerability is most relevant to internet-facing deployments. While internal networks are generally safer, you should still evaluate your setup, as MQTT brokers are sometimes reachable within internal segments that lack strict segmentation.

When should I start addressing this issue?

You should begin by identifying all running instances of the affected OpenRemote core. Once you have a list of deployments, assess which ones have network exposure and the level of business criticality for the devices they manage. Use this information to coordinate with system owners for remediation.

References