Skip to main content
VulnerabilityPublished Updated

CVE-2026-49278: RocketChat Rocket.Chat · Improper Authorization

Affects RocketChat Rocket.ChatSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
6.7Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
RocketChatRocket.ChatAffected
  • >=8.5.0-rc.0 <8.5.0
Fixed in
  • 8.5.0
RocketChatRocket.ChatAffected
  • >=8.4.0-rc.0 <8.4.2
Fixed in
  • 8.4.2
RocketChatRocket.ChatAffected
  • >=8.3.0-rc.0 <8.3.4
Fixed in
  • 8.3.4
RocketChatRocket.ChatAffected
  • >=8.2.0-rc.0 <8.2.4
Fixed in
  • 8.2.4
RocketChatRocket.ChatAffected
  • >=8.1.0-rc.0 <8.1.5
Fixed in
  • 8.1.5
RocketChatRocket.ChatAffected
  • >=8.0.0-rc.0 <8.0.6
Fixed in
  • 8.0.6

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.

References

Community reviews

Loading reviews…