Improper input validation in Rocket.chat
CVE-2026-65645
- CVSS v3
- 4.3 Medium
- Public exploits
- None known
- EPSS
- 0.003 · 28.6th percentile
- Published
- 2026-08-21
Rocket.Chat in versions before 8.8.0, 8.7.1, 8.6.2, 8.5.3, 8.4.6. 8.3.8, 8.2.8, 8.1.8, and 7.10.15, the Meteor DDP methods getThreadsList and getThreadMessages accept rid / tmid as raw, untyped parameters with no schema validation. A MongoDB operator object (e.g. {"$gt": "4"}) can be substituted for a string room-id or message-id. The authorization check resolves to a room the attacker already has access to, while the downstream data query fans out across all rooms - disclosing private thread parents and their full reply content to any low-privilege authenticated user.
The REST route chat.getThreadsList was patched in v5.0 (HackerOne report #1446767) by adding rid: {type:'string'} AJV validation. The equivalent DDP method was never given the same fix and remains exploitable
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- Low
PR:L - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- Low
C:L - Integrity
- None
I:N - Availability
- None
A:N
EPSS exploit prediction
EPSS 0.003, 28.6th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Rocket.chat — versions 8.7.0
Weakness classification (CWE)
References
- hackerone.com/reports/3852135 (Third Party Advisory, Issue Tracking)
- github.com/RocketChat/Rocket.Chat/pull/41814 (Patch, Vendor Advisory)