Rocket.Chat's POST /api/v1/chat.sendMessage endpoint improperly validates nested message properties, allowing
Source GCVE Database
Not known to be exploited : upgrade to 9.0.0 soon.
Data as of 20 Nov 2026, 22:45 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 9.0.0
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade Rocket.Chat to 9.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Rocket.ChatRocket.Chat | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict access to the chat.sendMessage endpoint to trusted users and monitor for suspicious message metadata injection attempts.
Description
A vulnerability in Rocket.Chat's POST /api/v1/chat.sendMessage endpoint allows authenticated users with standard privileges to inject arbitrary message metadata. This improper validation of nested message properties can result in persistent denial of service at the room level, stored HTML/iframe injection, unauthorized changes to other users' private starred messages, permission bypass, spoofing of pinned message attribution, forged edit attribution, and invisible user mentions.