Is CVE-2026-49278 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-49278 being exploited in the wild.

How severe is CVE-2026-49278?

Medium severity, with a CVSS score of 6.7, published 24 June 2026.

Which products and versions are affected?

Rocket.Chat < 7.10.12, 7.11.0-rc.0 to < 7.13.8, 8.0.0-rc.0 to < 8.0.6, 8.1.0-rc.0 to < 8.1.5, 8.2.0-rc.0 to < 8.2.4, 8.3.0-rc.0 to < 8.3.4, 8.4.0-rc.0 to < 8.4.2, 8.5.0-rc.0 to < 8.5.0.

Is there a fix for CVE-2026-49278?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-49278 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-49278?

Check whether you run Rocket.Chat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49278: Rocket.Chat token disclosure and visitor impersonation in visitors.info

Q: Which products and versions are affected?

Rocket.Chat < 7.10.12, 7.11.0-rc.0 to < 7.13.8, 8.0.0-rc.0 to < 8.0.6, 8.1.0-rc.0 to < 8.1.5, 8.2.0-rc.0 to < 8.2.4, 8.3.0-rc.0 to < 8.3.4, 8.4.0-rc.0 to < 8.4.2, 8.5.0-rc.0 to < 8.5.0.

Q: Is there a fix for CVE-2026-49278?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-49278 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-49278?

Check whether you run Rocket.Chat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49278 · Severity: medium · CVSS 6.7 · Published 2026-06-24

Rocket.Chat is a communications platform used for team collaboration and customer support. A security flaw in the visitor information system allows authorized staff members to access sensitive security tokens belonging to website visitors they are not supposed to manage. An attacker with staff-level access could use these leaked tokens to impersonate visitors, potentially accessing private chat histories or performing actions on their behalf.

Technologies: Rocket.Chat. Vendors: Rocket.Chat.

Quick answers

Is CVE-2026-49278 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-49278 being exploited in the wild.
How severe is CVE-2026-49278?: Medium severity, with a CVSS score of 6.7, published 24 June 2026.
Which products and versions are affected?: Rocket.Chat < 7.10.12, 7.11.0-rc.0 to < 7.13.8, 8.0.0-rc.0 to < 8.0.6, 8.1.0-rc.0 to < 8.1.5, 8.2.0-rc.0 to < 8.2.4, 8.3.0-rc.0 to < 8.3.4, 8.4.0-rc.0 to < 8.4.2, 8.5.0-rc.0 to < 8.5.0.
Is there a fix for CVE-2026-49278?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-49278 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-49278?: Check whether you run Rocket.Chat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An improper authorization vulnerability (CWE-285) exists in the Rocket.Chat 'visitors.info' API endpoint. While the endpoint requires the 'view-l-room' permission, it fails to restrict access based on the caller's authorized room, department, or queue scope. By providing a specific 'visitorId', an authenticated attacker can retrieve a full visitor object that includes the visitor's bearer token, contact fields, and network metadata. This leaked token can be used to impersonate the visitor. The issue is resolved in 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.

Affected products

RocketChat Rocket.Chat < 7.10.12, 7.11.0-rc.0 to < 7.13.8, 8.0.0-rc.0 to < 8.0.6, 8.1.0-rc.0 to < 8.1.5, 8.2.0-rc.0 to < 8.2.4, 8.3.0-rc.0 to < 8.3.4, 8.4.0-rc.0 to < 8.4.2, 8.5.0-rc.0 to < 8.5.0

Timeline

2026-05-25: advisory: GitHub Security Advisory published by Rocket.Chat
2026-06-24: disclosed: CVE published to NVD

References

https://github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-cqj7-h8cj-jmf2

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.