Skip to main content
Menu
CVEs

OpenRemote Manager authentication bypass in MQTT device provisioning

Affects OpenRemote core before 1.34.0 when X.509 MQTT provisioning is used and the target device is already provisioned. Fixed in 1.34.0.

CVE-2026-134287Published November 21, 2026, updated

9.2CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 1.34.0
Who is exposed
Not reported

Summary

Written by a model

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.

Who should check

Teams running OpenRemote core (io.openremote:openremote-manager) 1.33.0 or earlier that use X.509 MQTT device provisioning.

“OpenRemote core before 1.34.0 contains an authentication bypass vulnerability”

vulncheck.com

What to do

Upgrade to a fixed version: 1.34.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134287 (OpenRemote before 1.34.0 Authentication Bypass via X.509 MQTT Provisioning), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134287 (entry last updated 2026-11-21):
Affected:
- Maven package io.openremote:openremote-manager: fixed in 1.34.0
Fixed versions: 1.34.0.
Conditions (all must be true for the bug to be hit):
- X.509 MQTT provisioning is in use and the target device has already been provisioned. (source: https://github.com/openremote/core/security/advisories/GHSA-7jp3-2229-xgqj)
- The attacker must know the target device's public PEM certificate and device ID. (source: https://github.com/openremote/core/security/advisories/GHSA-7jp3-2229-xgqj)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134287 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134287 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/openremote/core/security/advisories/GHSA-7jp3-2229-xgqj
- https://www.vulncheck.com/advisories/openremote-before-1.34.0-authentication-bypass-via-x-509-mqtt-provisioning
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134287
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134287"}.

Affected versions

cve.now Index

36Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach10/20Affects Maven packages
  • Severity9.2/10CVSS 9.2
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active
  • Would score about 41 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · openremote/core · Advisory GHSA-7jp3-2229-xgqj
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134287
RecordNVD · CVE-2026-134287
Other links 1
Linkvulncheck.com · advisories/openremote-before-1.34.0-authentication-bypass-via-x-509-mqtt-provisioning

Questions about CVE-2026-134287

Is CVE-2026-134287 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

An attacker can impersonate an already provisioned device through X.509 MQTT provisioning and then act as that device's service account. That gives them the device's permissions, such as reading and modifying its assets and attributes.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134287?

io.openremote:openremote-manager (Maven): before 1.34.0.

Source: cve.now feed data

Am I affected, and how do I check?

Versions of OpenRemote core before 1.34.0 are affected, but only in deployments that use X.509 MQTT provisioning with a device that has already been provisioned. Checking the core version in use and whether X.509 MQTT provisioning is configured shows whether a deployment fits that setup.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134287?

Upgrade OpenRemote core to 1.34.0 or later, which contains the fix.

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.