OpenRemote remote disconnect of MQTT sessions across realms
- Exploited
- No known exploitation
- Fix
- Fixed in 1.31.0
- Who is exposed
- Not reported
Summary
OpenRemote, an open-source internet-of-things platform, has a flaw that lets an attacker disconnect other users' MQTT sessions across realm boundaries, disrupting MQTT connectivity without revealing session data. The attack can be carried out remotely, without logging in, through a disconnect route that lacks an ownership check.
Written by a model
Original description
OpenRemote is an open-source internet-of-things platform. Prior to 1.31.0, an authenticated user who obtains another user's MQTT session ID can disconnect that session across realm boundaries through the GET route GET {realm}/disconnect/{sessionID}. In manager/src/main/java/org/openremote/manager/security/UserResourceImpl.java, disconnectUserSession ignores the requested realm and calls mqttBrokerService.disconnectSession(sessionID) without checking session ownership; model/src/main/java/org/openremote/model/security/UserResource.java exposes the route without an @RolesAllowed restriction. The earlier cross-realm read-method guards did not cover this disconnect method, and same-realm users can also disconnect sessions they do not own. Session IDs are not trivially brute-forceable but may be exposed through monitoring, logs, or correlated API calls, and the unauthorized disconnect can disrupt MQTT connectivity across tenant boundaries without directly disclosing session data. This issue is fixed in 1.31.0.
What to do
Upgrade to a fixed version: 1.31.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-104885 (OpenRemote: Cross-realm MQTT session disconnect without authorization), 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-104885 (entry last updated 2026-11-19):
Affected:
- openremote openremote: fixed in 1.31.0
Fixed versions: 1.31.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-104885 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104885 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/openremote/core/security/advisories/GHSA-3h6w-xcw3-9xjj
- https://github.com/openremote/core/commit/51dce18d9e00d671a5e032d942ece186bdada560
- https://github.com/openremote/core/releases/tag/1.31.0
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-104885
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-104885"}.Affected versions
- openremote openremotefixed in 1.31.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · openremote/core · Advisory GHSA-3h6w-xcw3-9xjj |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-104885 |
| Record | NVD · CVE-2026-104885 |
| Other links 2 | |
| Repository | GitHub · openremote/core · Commit 51dce18d |
| Repository | GitHub · openremote/core · Release 1.31.0 |
Questions about CVE-2026-104885
Is CVE-2026-104885 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
Which versions are affected by CVE-2026-104885?
openremote: before 1.31.0.
Source: cve.now feed data
How do I fix CVE-2026-104885?
Upgrade to a fixed version: 1.31.0.
Source: cve.now feed data
Related
- CVE-2026-39842OpenRemote is Vulnerable to Expression Injection
- CVE-2026-66013OpenRemote before 1.26.2 Authentication Bypass via Console Registration
- CVE-2026-114661OpenRemote 1.2.0 before 1.31.0 Missing Authorization in Gateway Tunnel Endpoints
- CVE-2026-124436OpenRemote before 1.32.2 Improper Authorization Allows Realm Admins to Modify Global Resources
- CVE-2026-56784OpenRemote < 1.25.0 IDOR via Bulk Alarm Deletion Endpoint
- CVE-2026-81679OpenRemote before 1.28.0 Cross-Realm Information Disclosure via Notification API
No corrections so far. Something wrong on this page? Report an error.