Answer in brief
CVE-2026-72918 records a Unknown severity vulnerability in Rocket.Chat: Insecure implementation of websocket notifications. The current sources do not mark it as known exploited. The current feed maps RocketChat/Rocket.Chat (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps RocketChat/Rocket.Chat (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| RocketChat/Rocket.Chatgeneric | < 7.10.14 || >= 8.0.0, < 8.0.8 || >= 8.1.0, < 8.1.7 || >= 8.2.0, < 8.2.7 || >= 8.3.0, < 8.3.7 || >= 8.4.0, < 8.4.5 || >= 8.5.0, < 8.5.2 || >= 8.6.0, < 8.6.1 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72918 records a Unknown severity vulnerability in Rocket.Chat: Insecure implementation of websocket notifications. The current sources do not mark it as known exploited. The current feed maps RocketChat/Rocket.Chat (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps RocketChat/Rocket.Chat (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| RocketChat/Rocket.Chatgeneric | < 7.10.14 || >= 8.0.0, < 8.0.8 || >= 8.1.0, < 8.1.7 || >= 8.2.0, < 8.2.7 || >= 8.3.0, < 8.3.7 || >= 8.4.0, < 8.4.5 || >= 8.5.0, < 8.5.2 || >= 8.6.0, < 8.6.1 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.