# CVE-2026-49278: Rocket.Chat: Livechat Visitor Profile Disclosure Leaks Bearer Token and Enables Visitor Impersonation

> Rocket.Chat leaks Bearer tokens in visitor profile responses, allowing attackers to impersonate visitors and access sensitive data.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-cqj7-h8cj-jmf2

## What is CVE-2026-49278?

CVE-2026-49278 is a medium-severity vulnerability in RocketChat Rocket.Chat, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-49278?


## How do I fix CVE-2026-49278?

No fix has been published for CVE-2026-49278 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49278 being exploited?

There is no known exploitation of CVE-2026-49278 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49278 and fix it if it is affected.

What it is: CVE-2026-49278 is a medium-severity vulnerability in RocketChat Rocket.Chat, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49278 in the wild and no public exploit code.

Affected product: RocketChat Rocket.Chat. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49278/ (Markdown: https://insights.sbomify.com/CVE-2026-49278/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49278
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49278
- OSV: https://osv.dev/vulnerability/CVE-2026-49278

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49278/
Summaries are generated and may contain mistakes; the official description above is the record.