CVE-2026-49278: CWE-285: Improper Authorization in RocketChat Rocket.Chat
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.
AI Analysis
Technical Summary
Rocket.Chat versions prior to 7.10.12 and several incremental versions up to but excluding 8.5.0 contain an improper authorization vulnerability (CWE-285) in the visitors.info endpoint. This endpoint returns a token in its response, which is unnecessary and considered a security risk. The vulnerability allows unauthorized exposure of sensitive token information. The issue is fixed 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.
Potential Impact
The vulnerability results in unauthorized disclosure of a token through the visitors.info API endpoint, potentially allowing attackers with high privileges to access sensitive information. The CVSS score of 6.7 reflects a medium severity with high impact on confidentiality and integrity, and low impact on availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
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.
CVE-2026-49278: CWE-285: Improper Authorization in RocketChat Rocket.Chat
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.
CVSS v3.1
Score 6.7medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Rocket.Chat versions prior to 7.10.12 and several incremental versions up to but excluding 8.5.0 contain an improper authorization vulnerability (CWE-285) in the visitors.info endpoint. This endpoint returns a token in its response, which is unnecessary and considered a security risk. The vulnerability allows unauthorized exposure of sensitive token information. The issue is fixed 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.
Potential Impact
The vulnerability results in unauthorized disclosure of a token through the visitors.info API endpoint, potentially allowing attackers with high privileges to access sensitive information. The CVSS score of 6.7 reflects a medium severity with high impact on confidentiality and integrity, and low impact on availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-28T20:07:58.861Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3c4ce24853345fc1df8d6c
Added to database: 06/24/2026, 21:32:18 UTC
Last enriched: 07/01/2026, 22:34:55 UTC
Last updated: 08/08/2026, 12:41:11 UTC
Views: 75
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.