CVE-2026-72918

Rocket.Chat: Insecure implementation of websocket notifications

Published Aug 10, 2026 CVSS 3.1 · 5.4 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 stream-notify-user stream in the WebSocket protocol allows an authenticated user to write arbitrary notification bodies because the sender is not checked, and the client-side UI can create an ephemeral fake message in another user's currently open chat. 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 exists in the WebSocket stream used for user notifications. An authenticated user can craft arbitrary notification objects because the stream’s sender field is not validated. The client UI can then display a fabricated message in another user’s active chat window. This flaw allows a malicious user to inject messages that appear to come from others, potentially causing confusion, misinformation, or social engineering. The weakness is a classic Missing Authorization issue (CWE‑862).

Affected Systems

The affected product is Rocket.Chat the open‑source communications platform. Versions before 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 are vulnerable.

Risk and Exploitability

The CVSS score is 5.4, indicating moderate severity. No EPSS data is available and the vulnerability is not listed in CISA’s KEV catalog. Exploitation requires authentication and can be performed by any user with normal access. The risk is primarily to message integrity and potential privacy concerns through deception, rather than to system compromise or data exfiltration.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply an upgrade of Rocket.Chat to 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, which removes the sender validation flaw.
  • Review and tighten user role permissions so that only users with elevated privileges can use the stream‑notify‑user WebSocket stream; revoke this capability from regular users if possible.
  • Monitor chat activity for suspicious or fabricated notifications and consider disabling the stream‑notify‑user notification stream via server configuration until the patch is applied.

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 stream-notify-user stream in the WebSocket protocol allows an authenticated user to write arbitrary notification bodies because the sender is not checked, and the client-side UI can create an ephemeral fake message in another user's currently open chat. 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: Insecure implementation of websocket notifications
Weaknesses CWE-862
References
Metrics cvssV3_1

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

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 11, 2026, 4:04 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