# CVE-2026-45757: Rocket.Chat: users.deactivateIdle` deactivates accounts without revoking existing login tokens

> Deactivated users retain valid login tokens, allowing them to bypass authentication and access authenticated endpoints.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-6g3w-vg5p-w892

## What is CVE-2026-45757?

CVE-2026-45757 is a low-severity authentication bypass vulnerability in RocketChat Rocket.Chat, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### 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, Rocket.Chat allows users deactivated through users.deactivateIdle to keep using already-issued login tokens. A user that an administrator has marked inactive for idleness can still access authenticated REST endpoints with the old token. 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-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-45757 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45757 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45757 is a low-severity authentication bypass vulnerability in RocketChat Rocket.Chat, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45757 exists.

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-45757/ (Markdown: https://insights.sbomify.com/CVE-2026-45757/index.md)
```

## Sources

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

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