Rocket.Chat up to 8.7.x Meteor DDP getThreadsList/getThreadMessages rid/tmid improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 2.70 |
Summary
A vulnerability labeled as problematic has been found in Rocket.Chat up to 8.7.x. The affected element is the function getThreadsList/getThreadMessages of the component Meteor DDP. The manipulation of the argument rid/tmid results in improper authorization.
This vulnerability is identified as CVE-2026-65645. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in Rocket.Chat up to 8.7.x. It has been classified as problematic. Affected is the function getThreadsList/getThreadMessages of the component Meteor DDP. The manipulation of the argument rid/tmid with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. CVE summarizes:
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
The advisory is available at hackerone.com. This vulnerability is traded as CVE-2026-65645 since 07/22/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1548.002 by the MITRE ATT&CK project.
Upgrading to version 7.10.15, 8.2.8, 8.3.8, 8.4.6, 8.5.3, 8.6.2, 8.7.1 or 8.8.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-63805). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
- 7.10.0
- 7.10.1
- 7.10.2
- 7.10.3
- 7.10.4
- 7.10.5
- 7.10.6
- 7.10.7
- 7.10.8
- 7.10.9
- 7.10.10
- 7.10.11
- 7.10.12
- 7.10.13
- 7.10.14
- 8.0
- 8.1
- 8.1.0
- 8.1.1
- 8.1.2
- 8.1.3
- 8.1.4
- 8.1.5
- 8.1.6
- 8.1.7
- 8.2
- 8.2.0
- 8.2.1
- 8.2.2
- 8.2.3
- 8.2.4
- 8.2.5
- 8.2.6
- 8.2.7
- 8.3
- 8.3.0
- 8.3.1
- 8.3.2
- 8.3.3
- 8.3.4
- 8.3.5
- 8.3.6
- 8.3.7
- 8.4
- 8.4.0
- 8.4.1
- 8.4.2
- 8.4.3
- 8.4.4
- 8.4.5
- 8.5
- 8.5.0
- 8.5.1
- 8.5.2
- 8.6
- 8.6.0
- 8.6.1
- 8.7
- 8.7.0
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Rocket.Chat 7.10.15/8.2.8/8.3.8/8.4.6/8.5.3/8.6.2/8.7.1/8.8.0
Timeline
07/22/2026 CVE reserved08/21/2026 Advisory disclosed
08/21/2026 VulDB entry created
08/21/2026 VulDB entry last update
Sources
Advisory: hackerone.comStatus: Confirmed
CVE: CVE-2026-65645 (🔒)
GCVE (CVE): GCVE-0-2026-65645
GCVE (VulDB): GCVE-100-394026
EUVD: 🔒
Entry
Created: 08/21/2026 05:31Updated: 08/21/2026 06:27
Changes: 08/21/2026 05:31 (56), 08/21/2026 06:27 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.