CVE intelligence and bounded remediation
CVE-2026-49278 — Rocket.Chat is an open-source, secure, fully customizable communications platform
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.
- Severity
- Medium
- CVSS
- 6.7 (3.1)
- Published
- 2026-06-24
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-285
Affected products
No browser-safe affected-product rows are available.
Matched remediation archetype
Authorization bypass, IDOR, and cross-tenant access
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Map object and action authorization checks across API, UI, batch, import/export, and background-job paths.
- Identify tenant, ownership, role, and policy boundaries for affected resources and administrative operations.
- Use synthetic fixtures to compare intended access matrices without accessing another user's real data.
Remediate safely
- Enforce server-side authorization at each resource access and state transition using the authenticated principal and trusted tenant context.
- Scope data queries by tenant and ownership; treat client-supplied identifiers, roles, and policy claims as untrusted.
- Add deny-by-default policy tests for horizontal and vertical access across every affected transport.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.