CVE-2026-49278: RocketChat Rocket.Chat · Improper Authorization
Affects RocketChat Rocket.ChatSource CVE Database V5
Not known to be exploited · CVSS 6.7 Medium · fixed in 8.5.0 : update RocketChat Rocket.Chat when convenient.
Data as of 5 Nov 2026, 11:40 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.7 |
|---|
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.5.0, 8.4.2, 8.3.4 +5
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 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 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
AI-suggested
A fix is available and has been implemented in Rocket.Chat versions 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12. Users should upgrade to one of these versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12, in the visitors.info endpoint, https://developer.rocket.chat/apidocs/get-visitor-information-by-id-1, token is returned in the response. It looks like there's no use case for the token to be present in the response and it would be a good security practice to remove it altogether. This vulnerability is fixed in 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12.