Vulnerability in Rocketchat (CVE-2026-65645)
Summary
Vulnerability in Rocketchat (CVE-2026-65645). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.0 or later.
Original description
The description as published by the source.
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
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-65645 has been found in Rocketchat.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade Rocketchat to 5.0 or later.
If unsure, ask your IT team or search "Rocketchat CVE-2026-65645" on the vendor's site.
CVE-2026-65645 (Rocketchat) — CWE-20 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in Rocketchat.
Check the vendor advisory for the affected versions of Rocketchat.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 5.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Rocketchat' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Rocketchat' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Rocketchatを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Rocketchat to 5.0ステージング環境で 5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web hackerone.com
- web github.com