# CVE-2026-45687: Rocket.Chat: Authenticated Arbitrary Data Export Theft via Mass Assignment in sendFileMessage

> Authenticated attackers can steal arbitrary data or modify records by exploiting mass assignment in the sendFileMessage method.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-fhc2-x8cp-c5ch

## What is CVE-2026-45687?

CVE-2026-45687 is a high-severity vulnerability in RocketChat Rocket.Chat, published on 24 Jun 2026. Any signed-in user can exploit it over the network, 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.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11, Rocket.Chat's sendFileMessage DDP method passes the entire attacker-supplied file object into Uploads.updateFileComplete, which merges it directly into a MongoDB $set update via Object.assign. There is no allow-list of writable fields. An attacker can therefore rewrite any column on their own upload record, notably store and the store-specific path fields. This vulnerability is fixed in 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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


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

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

## Is CVE-2026-45687 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45687 is a high-severity vulnerability in RocketChat Rocket.Chat, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45687 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-45687/ (Markdown: https://insights.sbomify.com/CVE-2026-45687/index.md)
```

## Sources

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

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