# CVE-2026-65645: Missing authorization in Rocket.Chat

> Low-privilege users can access private thread data in Rocket.Chat due to missing input validation in DDP methods.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-gw74-gwm4-8crp

## What is CVE-2026-65645?

CVE-2026-65645 is a medium-severity missing authorization vulnerability in Rocket.chat Rocket.chat, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-65645?

It affects 1 product.


Products: Rocket.chat Rocket.chat.

## How do I fix CVE-2026-65645?

No fix has been published for CVE-2026-65645 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-65645 being exploited?

There is no known exploitation of CVE-2026-65645 in the wild and no public exploit code.

## Other vulnerabilities in Rocket.chat Rocket.chat

- [CVE-2026-58066](https://insights.sbomify.com/CVE-2026-58066/): Auth bypass in Rocket.Chat (critical 9.8)
- [CVE-2026-29198](https://insights.sbomify.com/CVE-2026-29198/): SQL injection in Rocket.Chat (critical 9.8)
- [CVE-2023-28316](https://insights.sbomify.com/CVE-2023-28316/): Security feature bypass in Rocket.Chat (critical 9.8)
- [CVE-2022-44567](https://insights.sbomify.com/CVE-2022-44567/): Command injection in Rocket.chat - Electron Desktop (critical 9.8)
- [CVE-2021-22910](https://insights.sbomify.com/CVE-2021-22910/): Code injection in Rocket.Chat server (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65645 and fix it if it is affected.

What it is: CVE-2026-65645 is a medium-severity missing authorization vulnerability in Rocket.chat Rocket.chat, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65645 in the wild and no public exploit code.

Affected product: Rocket.chat Rocket.chat. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-65645/ (Markdown: https://insights.sbomify.com/CVE-2026-65645/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-65645
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-65645
- OSV: https://osv.dev/vulnerability/CVE-2026-65645

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-65645/
Summaries are generated and may contain mistakes; the official description above is the record.