dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-49278

MEDIUM · 6.7 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Rocket.Chat's visitors.info API endpoint incorrectly returns a visitor token in the response. This sensitive token should not be exposed as it could be used for visitor impersonation or session hijacking. The fix involves removing the token field from the API response.

MitigationUpgrade Rocket.Chat to version 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, or 7.10.12 or later, which removes the token from the visitors.info endpoint response.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Rocket.Chat installation and version
    Check the installed Rocket.Chat version via package manager, docker image tag, or by accessing the /api/info endpoint (GET /api/info) which returns version information in the response body.
    Affected if The installed version is older than 7.10.12, or falls between 7.10.12 - 7.13.7, 7.13.8 - 8.0.5, 8.1.0 - 8.1.4, 8.2.0 - 8.2.3, 8.3.0 - 8.3.3, 8.4.0 - 8.4.1, or 8.5.0 (which are all vulnerable versions).
  2. Confirm visitors.info API endpoint accessibility
    Verify the Rocket.Chat server is accessible via HTTP/HTTPS and that you have authentication credentials (user account) to make API calls to the server.
    Affected if The server is reachable and you have valid API credentials to query the visitors endpoint.
  3. Test visitors.info endpoint for token exposure
    Make an authenticated API request to the visitors.info endpoint (GET /api/v1/visitors.info) with a valid visitorId parameter, then inspect the JSON response body for the presence of a 'token' field.
    Affected if The response contains a 'token' field with a value - this indicates the vulnerability is present and the sensitive token is being exposed.

A user is affected if their Rocket.Chat version is below the fixed releases AND the visitors.info API response contains an exposed visitor token field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Rocket.Chat to version 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, or 7.10.12 or later, which removes the token from the visitors.info endpoint response.

Recommended fix High confidence

Upgrade to Rocket.Chat 8.5.0 (or latest 8.x stable). For older major version branches, upgrade to 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, or 7.10.12 as appropriate for your branch.

  1. 1. Backup your Rocket.Chat database and configuration before upgrading.
  2. 2. Review the release notes for the target version (e.g., 8.5.0 or 8.4.2) to check for any migration requirements or breaking changes.
  3. 3. Stop the Rocket.Chat service.
  4. 4. Upgrade Rocket.Chat to version 8.5.0 (or the latest 8.x stable release) using your deployment method (e.g., Docker, snap, or package manager).
  5. 5. Start the Rocket.Chat service.
  6. 6. Verify that the visitors.info endpoint no longer returns the token in the response.
  7. 7. Test that normal chat functionality continues to work as expected.
Caveat Patch releases typically have minimal breaking changes, but review release notes for any migration steps required.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49278 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49278 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data