Skip to content
CVE Alert: CVE-2026-134287 – openremote

CVE Alert: CVE-2026-134287 – openremote

Redpacketsecurity •admin • November 22, 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.

Urgent for deployments where the MQTT provisioning interface is reachable: an unauthenticated attacker may gain device-level access and affect managed assets.

The compromised service identity could expose sensitive asset data and permit unauthorised changes, with potential operational disruption. The likely impact depends on the assets and permissions assigned to that identity; evidence of wider system compromise is not provided.

### Most likely attack path

The attack is network-based, requires no prior privileges or user interaction, and has low complexity, but a target-specific provisioning condition must be present. An attacker needs access to the relevant MQTT path and enough information to identify a provisioned device; the stated scope is unchanged, so lateral movement beyond the service’s own authority is not established.

### Who is most exposed

Prioritise internet- or partner-accessible deployments, and installations where MQTT provisioning is enabled or broker access is broadly available. Exposure cannot be confirmed without deployment configuration and broker reachability data.

Review broker logs for anonymous connections publishing to provisioning topics.

Alert on provisioning attempts for existing device identities or certificates.

Check for unexpected device service-account sessions and asset reads or writes.

Correlate broker activity with changes to device and asset records.

### Mitigation and prioritisation

Upgrade promptly to a fixed release; verify the deployed core version and package inventory.

Until patched, disable provisioning if feasible or restrict broker and topic access to trusted networks and authenticated clients.

Review and reduce service-account permissions; rotate credentials or certificates if suspicious activity is found.

Test the upgrade in staging, then deploy under change control; monitor provisioning and asset changes afterwards.

KEV, SSVC exploitation and EPSS data were not supplied, so exploitation prioritisation remains uncertain; check these signals before final triage.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

The full story

This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.

Extracted Entities

Attack Types (1)

Platforms (1)