Rocket.Chat: Improper Authentication
CVE-2026-48929 is a high-severity improper authentication vulnerability in Rocket.Chat, with a CVSS 3.0 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 8.5.1, 8.4.4, 8.3.6 as the first without the flaw, so updating Rocket.Chat to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.72% chance of exploitation within 30 days, higher than 55% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Rocket.Chat to 8.5.1 or 8.4.4 or 8.3.6 or 8.2.6, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Rocket.Chat | Rocket.Chat | before 8.5.1; before 8.4.4; before 8.3.6; before 8.2.6; before 8.1.6; before 8.0.7; before 7.13.9; before 7.10.13 | 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (hackerone.com).
Official description
Rocket.Chat in versions <8.5.1, <8.4.4, <8.3.6, <8.2.6, <8.1.6, <8.0.7, <7.13.9, and <7.10.13 is vulnerable to unauthenticated file deletion. The deleteFileMessage Meteor method permanently deletes any uploaded file by ID without requiring authentication. When called via an unauthenticated DDP WebSocket connection, Meteor.userId() returns null, causing the authorization check to be skipped. Execution falls through to FileUpload.getStore('Uploads').deleteById(fileID), which removes the file from storage and database unconditionally. File IDs are discoverable from public channel message payloads and download URLs.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/RocketChat/Rocket.Chat/pull/40889/Issue Tracking, Third Party Advisory
Third-party and government advisories
- hackerone.com/reports/3611837Third Party Advisory
Other vulnerabilities in Rocket.Chat
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.3 Critical severity
- 7.5 High severity
- 9.8 Critical severity
Recent Improper Authentication vulnerabilities
- 8.1 High severity
- 8.1 High severity
- 9.8 Critical severity
- 8.2 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.