MediumGHSA-3h6w-xcw3-9xjjCVE-2026-104885

OpenRemote: Cross-realm MQTT session disconnect without authorization

Published 20 Nov 2026 · Updated 20 Nov 2026

Is your project on an affected io.openremote:openremote-manager?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.31.0
Fixed in
1.31.0
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.openremote:openremote-manager -DdepVersion=1.31.0 -DforceVersion=true

Details

Summary

Cross-realm MQTT session disconnect without authorization

Vulnerability

The disconnectUserSession endpoint in UserResourceImpl.java (line 443) accepts a realm path parameter but ignores it entirely, performing no authorization or realm-boundary check before force-disconnecting an MQTT session. Any authenticated user from any realm can disconnect MQTT broker sessions belonging to users in other realms by supplying the target session ID.

File: manager/src/main/java/org/openremote/manager/security/UserResourceImpl.java, lines 443-447

@Override
public void disconnectUserSession(RequestParams requestParams, String realm, String sessionID) {
    if (!mqttBrokerService.disconnectSession(sessionID)) {
        throw new NotFoundException("User session not found");
    }
}

The REST interface at model/src/main/java/org/openremote/model/security/UserResource.java (line 201-204) maps this to GET {realm}/disconnect/{sessionID} with no @RolesAllowed annotation, so any authenticated user (not just admins) can call it.

Root Cause

CVE-2026-54641 (commit de89b8d) fixed cross-realm information disclosure in three read methods of the same file (get(), getUserClientRoles(), getUserRealmRoles()) and also added a realm check to getClientRoles(). The fix added throwIfCannotReadUserInRealm() and throwIfCannotAdminRealm() guards. However, disconnectUserSession was not patched and remains unprotected. Every other mutating method in this class has either a @RolesAllowed annotation on the interface or an explicit realm check in the implementation. This one has neither.

Proof of Concept

Given two realms, "master" and "building":

1. User A authenticates in the "building" realm (any role, no admin needed). 2. User B has an active MQTT session in the "master" realm with session ID S. 3. User A sends: GET /api/master/user/master/disconnect/S with their building-realm bearer token. 4. The handler ignores the realm path segments, looks up session S in the global connectionIDConnectionMap, and calls doForceDisconnect(). User B's MQTT connection is terminated.

Session IDs use the Netty ChannelId.asLongText() format (deterministic, partially sequential). While not trivially brute-forceable, IDs can leak through monitoring, logs, or correlated API calls. Within the same realm, any user (not just admins) can also disconnect sessions they should not have access to.

Impact

In a multi-tenant IoT deployment, an attacker authenticated in any realm can disrupt MQTT device connectivity in other realms. Since OpenRemote is used for building management, energy monitoring, and industrial IoT, forcibly disconnecting MQTT sessions can:

  • Knock IoT sensors and actuators offline across tenant boundaries
  • Disrupt safety-critical alarm monitoring (compounding the alarm IDOR fixed in CVE-2026-57168)
  • Cause denial of service against other tenants' device fleets

The method also uses HTTP GET for a destructive operation, making it susceptible to CSRF via image tags or link prefetch.

Suggested Fix

Add a realm administration check consistent with the pattern used elsewhere in this file:

@Override
public void disconnectUserSession(RequestParams requestParams, String realm, String sessionID) {
    throwIfCannotAdminRealm(realm);

    RemotingConnection connection = mqttBrokerService.getConnectionByID(sessionID);
    if (connection == null) {
        throw new NotFoundException("User session not found");
    }

    // Verify the session belongs to a user in the requested realm
    // before disconnecting

    if (!mqttBrokerService.disconnectSession(sessionID)) {
        throw new NotFoundException("User session not found");
    }
}

At minimum, add throwIfCannotAdminRealm(realm) as the first line, and consider adding a @RolesAllowed(Constants.WRITE_ADMIN_ROLE) annotation to the interface method. The HTTP method should also be changed from GET to DELETE.

AI tooling

AI assistance was used for the code audit and for drafting this report. The finding against the project's source at the location cited above was manually verified before reporting it, and the severity and impact assessment are the reporter's own.

Is GHSA-3h6w-xcw3-9xjj in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected io.openremote:openremote-manager, and gives you the command that fixes it.

More advisories for io.openremote:openremote-manager

  • HighCVE-2026-62238OpenRemote has Authenticated SQL Injection via Datapoint Crosstab Export · 6 Jul 2026
  • HighCVE-2026-54641OpenRemote has Cross-Realm User Information Disclosure in UserResourceImpl · 6 Jul 2026
  • MediumCVE-2026-49439OpenRemote read-only asset users can write predicted datapoints · 6 Jul 2026
  • CriticalCVE-2026-56120OpenRemote Manager: removeAlarms cross-realm IDOR (bulk delete) · 19 Jun 2026
  • HighCVE-2026-41166OpenRemote has Improper Access Control via updateUserRealmRoles function · 22 Apr 2026
  • HighCVE-2026-40882OpenRemote has XXE in Velbus Asset Import · 15 Apr 2026
All 8 advisories for io.openremote:openremote-manager

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.