CVE-2026-65645

MEDIUM
4.3
CVSS Score
Published: August 21, 2026 at 02:53 AM UTC
Updated: October 26, 2026 at 10:10 AM UTC
1 product affected across 1 vendorChat Rocket Chat

Using Rocket.Chat by Rocket.Chat?

Get instant alerts when new vulnerabilities affect Rocket.Chat - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 7.10.158.1.0 ≤ v < 8.1.88.2.0 ≤ v < 8.2.88.3.0 ≤ v < 8.3.88.4.0 ≤ v < 8.4.68.5.0 ≤ v < 8.5.38.6.0 ≤ v < 8.6.28.7.0
Affected range stops below 7.10.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.2.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.3.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.4.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.5.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.7.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.8.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

Third Party AdvisoryIssue Tracking
Source: cverecord
https://hackerone.com/reports/3852135
PatchVendor Advisory
Source: cverecord
https://github.com/RocketChat/Rocket.Chat/pull/41814

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.3MEDIUMCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card