dbcve.org
CWE-915Weakness · CWE-915

CVE-2026-45687

HIGH · 8.5 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 →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

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

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 sendFileMessage DDP method passes attacker-supplied file objects directly into Uploads.updateFileComplete without field validation, using Object.assign to merge into MongoDB $set updates. This allows attackers to overwrite columns on their own upload records, notably the 'store' field and store-specific path fields, through mass assignment.

MitigationUpgrade Rocket.Chat to version 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, or 7.10.11, which implement an allow-list of writable fields to prevent unauthorized column manipulation.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

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

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 server version
    Run the command: curl -s http://localhost:3000/api/info | jq '.version' or check the admin panel under 'Administration > Info'
    Affected if The version returned is prior to 8.5.0, or falls within 8.4.0-8.4.1, 8.3.0-8.3.3, 8.2.0-8.2.3, 8.1.0-8.1.4, 8.0.0-8.0.5, 7.13.0-7.13.7, or 7.10.0-7.10.11 (all versions before the fixed releases)
  2. Confirm DDP/WebSocket endpoint exposure
    Verify the Rocket.Chat Meteor DDP endpoint is accessible at /websocket or port 3000 by default. Check with: curl -I http://localhost:3000/websocket
    Affected if The endpoint responds, indicating the DDP interface is exposed (the vulnerability requires an authenticated DDP connection)
  3. Verify file upload capability is enabled
    Check if file upload feature is enabled in Administration > Settings > File Upload. Also verify the 'Uploads' collection exists in MongoDB: db.uploads.findOne()
    Affected if Uploads collection exists and file uploads are permitted (the flaw affects upload record modifications)
  4. Check MongoDB upload record structure
    Connect to MongoDB and inspect a sample upload record: db.uploads.findOne({}) - note the fields 'store' and any store-specific path fields
    Affected if Records contain writable store and path fields that could be modified via the vulnerable Object.assign in Uploads.updateFileComplete

You are affected if your Rocket.Chat version is any release prior to 8.5.0 (or one of the unpatched minor versions 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, or 7.10.11) AND the file upload feature is enabled, since the vulnerability allows authenticated users to modify their own upload record fields via the sendFileMessage DDP method.

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.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, or 7.10.11, which implement an allow-list of writable fields to prevent unauthorized column manipulation.

Recommended fix High confidence

8.5.0 (or 7.13.7 for 7.x LTS branch)

  1. Identify the currently installed Rocket.Chat version by checking the package.json or deployment configuration
  2. Determine which release branch is appropriate (7.x LTS or 8.x current stable)
  3. For 7.x branch: Upgrade to version 7.13.7 or later
  4. For 8.x branch: Upgrade to version 8.5.0 or later
  5. Backup the MongoDB database and Rocket.Chat data before performing the upgrade
  6. Follow the official Rocket.Chat upgrade documentation for your deployment method (snap, docker, or manual)
  7. After upgrade, verify the sendFileMessage DDP method now properly validates file object fields before MongoDB updates
Caveat Review Rocket.Chat release notes for potential breaking changes between your current version and the target upgrade version; major version jumps may require migration steps

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45687 — 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-45687 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