CVE-2026-65644: versions · Rocket.Chat
Source GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 8.8.0 : patch versions soon.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- versions before 8.8.0
- Patch
- Available – fixed in 8.8.0, 8.7.1, 8.6.2 +6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
AI-suggested
Until a fix is confirmed, restrict access to the Livechat visitor API endpoint or implement input sanitization on the 'name' field to prevent injection of malicious HTML. Avoid rendering untrusted input with dangerouslySetInnerHTML or apply proper escaping. Monitor vendor communications for official patches or updates.
Description
Rocket.Chat versions prior to 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 contain a vulnerability in the REST API endpoint POST /api/v1/livechat/visitor. This endpoint accepts an unauthenticated and unsanitized 'name' field for Livechat visitors, which is stored raw and later rendered in the Omnichannel Queue side panel using dangerouslySetInnerHTML. This allows injection of a clickable HTML link controlled by an attacker, potentially enabling social engineering attacks against agents viewing the queue.