Skip to content
OpenRemote core authentication bypass lets attackers impersonate provisioned MQTT devices (CVE-2026-134287)

OpenRemote core authentication bypass lets attackers impersonate provisioned MQTT devices (CVE-2026-134287)

First seen 22 Nov 2026, 17:14 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 22, 2026 at 17:14 UTC
  • •CVE-2026-134287 affects OpenRemote core versions before 1.34.0 and allows authentication as a provisioned device's service account.
  • •Per the GitHub advisory, the flaw lets an unauthenticated MQTT client use a known device's public certificate without holding its private key.
  • •Redpacketsecurity says impact is read and write access to assets permitted for the impersonated service identity.
  • •Exposure depends on whether MQTT provisioning is enabled and whether the broker is reachable; the articles do not report exploitation in the wild.
  • •Recommended steps are upgrading to 1.34.0 or later, disabling provisioning or restricting broker access, and reviewing service-account permissions.

CVE-2026-134287 affects OpenRemote core before 1.34.0, per Redpacketsecurity, and is described as an authentication bypass in UserAssetProvisioningMQTTHandler. According to the GitHub advisory GHSA-7jp3-2229-xgqj, the MQTT X.509 provisioning flow accepts a certificate copied into an ordinary MQTT message and uses it to authenticate the current connection without verifying that the sender holds the matching private key. An unauthenticated client that knows a provisioned device's public certificate could, per the advisory, authenticate as that device's existing service account by publishing to the provisioning request topic. Redpacketsecurity states the attacker could then read and modify assets, with impact depending on the permissions assigned to that service identity; it says evidence of wider system compromise is not provided. The attack requires network access to the MQTT provisioning path and a target-specific provisioning condition, and Redpacketsecurity notes exposure cannot be confirmed without deployment configuration data. Redpacketsecurity recommends upgrading to a fixed release, disabling provisioning or restricting broker access until patched, and reviewing service-account permissions. The articles do not report exploitation in the wild, and KEV, EPSS and SSVC data were not supplied.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-21
CVE-2026-134287 published
Published with a CVSS score of 9.2 against OpenRemote core before 1.34.0.
2026-11-22
Redpacketsecurity alert published
Redpacketsecurity published an alert describing the authentication bypass and recommended mitigations.
Redpacketsecurity
2026-11-22
GitHub security advisory published
Advisory GHSA-7jp3-2229-xgqj describes the root cause in the MQTT X.509 provisioning handler.
github.com

More articles in this cluster (3)

Following this threat?

Track CVE-2026-134287 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions are affected?
OpenRemote core versions before 1.34.0 are affected, according to Redpacketsecurity.
Is this being exploited?
The articles do not report exploitation in the wild, and no KEV or EPSS data was supplied.
What should we do first?
Upgrade to 1.34.0 or later; if that must wait, disable MQTT provisioning or restrict broker and topic access to trusted clients.