Vulnerability in Rocket.Chat (CVE-2026-55762)
Summary
Vulnerability in Rocket.Chat (CVE-2026-55762). Data can be tampered with by attackers. Exploitable via POST /api/v1/fingerprint. Mitigation: upgrade to 8.5.1 or later.
Original description
The description as published by the source.
Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13, the POST /api/v1/fingerprint REST endpoint enforces authentication (authRequired: true) but performs no authorization check. Any authenticated user — including a standard user role account — can call this endpoint with {"setDeploymentAs": "new-workspace"} to permanently deregister the workspace from Rocket.Chat Cloud. This wipes all cloud credentials, removes the workspace license, breaks push notifications for all users, and requires manual re-registration to recover. This vulnerability is fixed in 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13.
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-55762 has been found in Rocket.Chat.
Attackers can target a specific entry point like POST /api/v1/fingerprint over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade Rocket.Chat to 8.5.1 or later.
If unsure, ask your IT team or search "Rocket.Chat CVE-2026-55762" on the vendor's site.
CVE-2026-55762 (Rocket.Chat) — CWE-862 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/fingerprint
Patched: 8.5.1 — 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-862) exists in Rocket.Chat. Attackers reach the vulnerable code path via POST /api/v1/fingerprint.
Check the vendor advisory for the affected versions of Rocket.Chat. Attack surface: POST /api/v1/fingerprint.
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.
Update to 8.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v1/fingerprint requests with malformed payloads or SQL meta-characters. Run grep -r 'Rocket.Chat' . 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 'Rocket.Chat' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Rocket.Chatを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/v1/fingerprint' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v1/fingerprintへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Rocket.Chat to 8.5.1ステージング環境で 8.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v1/fingerprint on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov