CVE-2026-106075 json
Rocket.Chat's POST /api/v1/chat.sendMessage endpoint improperly validates nested message properties, allowing authenticated users with standard privileges to inject arbitrary message metadata that is persisted and trusted by the server and clients.
published yesterday modified yesterday also EUVD-2026-131717
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
Rocket.Chat's POST /api/v1/chat.sendMessage endpoint improperly validates nested message properties, allowing authenticated users with standard privileges to inject arbitrary message metadata that is persisted and trusted by the server and clients. This can lead to persistent room-level denial of service, stored HTML/iframe injection, unauthorized modification of other users' private starred messages, permission bypass and attribution spoofing for pinned messages, forged edit attribution, and invisible user mentions.
Patch / fix
- Rocket.Chat Rocket.Chat 9.0.0
Is CVE-2026-106075 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-21).
Affected products
- Rocket.Chat Rocket.Chat
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
Sources
- CVE List CVE-2026-106075
- NVD CVE-2026-106075
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.