Skip to content
Threat Brief

← All advisories

CVE-2026-104885

Medium 6.3No known exploitationFix available

OpenRemote: Cross-realm MQTT session disconnect without authorization

Vendor advisory: GHSA-3h6w-xcw3-9xjj

Record last updated

CVSS score

6.3

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 26% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-862

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
mavenio.openremote:openremote-managerall versions before 1.31.01.31.0GitHub Advisory Database
openremoteopenremote< 1.31.0Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by GitHub_M

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references