CVE-2026-134287 in OpenRemote
Summary
by MITRE • 11/21/2026
OpenRemote core before 1.34.0 contains an authentication bypass vulnerability in UserAssetProvisioningMQTTHandler that allows unauthenticated attackers to impersonate provisioned devices without proof of private key possession. Attackers can publish a known device's public certificate to the provisioning request topic, authenticating their anonymous MQTT connection as the device's service account to read and modify assets.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in OpenRemote core versions prior to 1.34.0 represents a critical authentication bypass within the UserAssetProvisioningMQTTHandler component of the platform. This flaw fundamentally undermines the security model designed for device provisioning over MQTT, allowing unauthenticated actors to impersonate legitimate provisioned devices without possessing the required private cryptographic keys. The core issue lies in how the handler validates incoming provisioning requests, specifically failing to enforce strict proof-of-possession checks that are standard practice in public key infrastructure and secure IoT communication protocols. By neglecting to verify that the entity initiating the request actually controls the private key corresponding to the presented certificate, the system accepts any connection where a known device's public certificate is published to the provisioning topic as valid authentication for that device identity.
From a technical perspective, this vulnerability stems from an improper implementation of mutual TLS or similar asymmetric authentication mechanisms within the MQTT broker integration layer. In secure IoT architectures, when a device connects using a client certificate, the server must verify not only that the certificate is signed by a trusted authority but also that the connecting party possesses the private key associated with that certificate through a cryptographic handshake process such as verifying a signature or completing a challenge-response mechanism. The flaw in OpenRemote allows an attacker to simply publish the public portion of a target device's certificate to the specific MQTT topic designated for provisioning requests. Because the handler does not validate the corresponding private key possession, it erroneously treats this anonymous connection as if it were authenticated by the legitimate service account associated with that device. This effectively nullifies the confidentiality and integrity guarantees provided by the PKI setup intended for these devices.
The operational impact of this vulnerability is severe, granting attackers full control over the impersonated assets within the OpenRemote ecosystem. Once an attacker successfully authenticates as a provisioned device using its public certificate without needing the private key, they gain access to read sensitive asset data and modify configurations or states associated with that device. This capability can lead to unauthorized surveillance if sensors are involved, manipulation of automated processes controlled by actuators, or potential pivoting into other parts of the network if those devices have broader connectivity privileges. The ability to impersonate multiple devices amplifies this risk, potentially allowing an attacker to disrupt operations across a large-scale IoT deployment simply by knowing the public certificates of target assets, which are often less protected than private keys and may be exposed through logs or configuration files.
This vulnerability aligns with CWE-287, Improper Authentication, as it involves a failure in verifying identity credentials during access control decisions. Furthermore, from an adversary behavior perspective, this technique corresponds to ATT&CK T1078 Valid Accounts, where attackers use legitimate system accounts or credentials to gain initial access and move laterally within the environment without triggering typical intrusion detection alerts associated with brute-force attacks or exploit code execution. The lack of proof-of-possession also touches upon CWE-326 Inadequate Encryption Strength if weak key exchange methods were used, but primarily it is a logic error in authentication validation rather than a weakness in cryptographic algorithms themselves.
To mitigate this vulnerability, organizations running OpenRemote versions earlier than 1.34.0 must upgrade to the patched version immediately where the UserAssetProvisioningMQTTHandler has been corrected to enforce strict proof-of-possession checks during device provisioning requests. Until an upgrade is feasible, administrators should implement network-level controls such as firewall rules or MQTT broker access control lists that restrict write and publish permissions on the provisioning topic exclusively to known IP addresses associated with legitimate provisioning infrastructure rather than open endpoints. Additionally, auditing logs for unusual patterns of certificate usage can help detect ongoing exploitation attempts where public certificates are repeatedly published by unauthorized sources. Ensuring that private keys remain strictly secured and never exposed in configuration files or logs is also critical to preventing attackers from obtaining the necessary components to attempt further attacks even if this specific bypass vector were patched.