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
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/RocketChat/Rocket.Chat/pull/41814 Patch, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 4.3 · rocket.chatNVD modified 2026-10-26 10:10
Affected (CPE criteria) 2
cpe:2.3:a:rocket.chat:rocket.chat:*:*:*:*:*:*:*:*cpe:2.3:a:rocket.chat:rocket.chat:8.7.0:*:*:*:*:*:*:*
References 2
- https://github.com/RocketChat/Rocket.Chat/pull/41814 Patch, Vendor Advisory
- https://hackerone.com/reports/3852135 Third Party Advisory, Issue Tracking