CVE-2026-72919

Rocket.Chat: Broken Access Control in channels.convertToTeam Allows Unauthorized Conversion of Public Channels into Teams

Published Aug 10, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, and 8.6.1, the channels.convertToTeam REST endpoint allows an authenticated registered user with the create-team permission to convert an unrelated public channel by supplying channelName instead of channelId because the edit-room permission is checked only for channelId. This issue is fixed in versions 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, and 8.6.1.

Analysis

AI-generated

Technical impact

The vulnerability allows an authenticated user with the create‑team permission to convert any unrelated public channel into a team by using the channelName parameter instead of the required channelId. Because the edit‑room permission is only checked against the channelId, the endpoint bypasses normal access controls. An attacker can therefore create new teams from arbitrary public channels, changing ownership and potentially exposing or isolating channel content without the knowledge of the original channel participants. The CWE-862 classification indicates a broken access control flaw.

Affected Systems

Rocket.Chat instances running any version earlier than 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, or 8.6.1 are affected. Administrators should verify the version of the deployed Rocket.Chat platform and apply the fix as soon as possible.

Risk and Exploitability

The CVSS score of 4.3 reflects a moderate severity; the EPSS score is not available, and the vulnerability is not listed in CISA KEV, suggesting limited exploitation evidence to date. Exploitation requires only an authenticated user with the create‑team privilege, which is often granted to non‑administrative roles. Once the endpoint is abused, the attacker can change the channel's privacy setting and membership, affecting confidentiality and availability of communications. The attack path involves logging into the platform, retrieving a public channel name, and calling the channels.convertToTeam REST endpoint with that name.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Rocket.Chat to at least version 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, or 8.6.1 to apply the vendor fix.
  • Restrict the create‑team permission to only trusted users or administrators to reduce the attack surface.
  • Disable or monitor the channels.convertToTeam endpoint if it is not required for business operations to prevent accidental misuse.

Generated by OpenCVE AI on August 11, 2026 at 00:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Rocketchat
Rocketchat rocket.chat
Vendors & Products Rocketchat
Rocketchat rocket.chat
Type Values Removed Values Added
Description Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, and 8.6.1, the channels.convertToTeam REST endpoint allows an authenticated registered user with the create-team permission to convert an unrelated public channel by supplying channelName instead of channelId because the edit-room permission is checked only for channelId. This issue is fixed in versions 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, and 8.6.1.
Title Rocket.Chat: Broken Access Control in channels.convertToTeam Allows Unauthorized Conversion of Public Channels into Teams
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 11, 2026, 2:26 PM
Reserved
Aug 10, 2026, 5:57 PM
Status
Awaiting Analysis
Published
Aug 10, 2026, 10:17 PM
Modified
Oct 24, 2026, 3:10 PM