Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-48616 – Unauthenticated File Disclosure (IDOR) in Livechat – Rocket.Chat < 8.5.1 / 8.4.4…

Be the first to know when new zero-days emerge:

Summary

CVE-2026-48616 is a critical broken access control (IDOR) vulnerability in Rocket.Chat’s Livechat file download endpoint that allows any unauthenticated remote attacker to enumerate and download files uploaded across all rooms on an affected server. The flaw affects all Rocket.Chat releases below 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, and carries a CVSS score of 9.3 (Critical).

Technical details

  • Root cause: The /file-upload/:fileId/:name endpoint authorizes Livechat access by validating a session triplet (rc_room_type=l, rc_rid, rc_token), but critically fails to verify that the supplied rc_rid actually corresponds to the room that owns the requested file. This is a classic Insecure Direct Object Reference (IDOR): an attacker can present a valid rc_rid from any Livechat session while requesting files belonging to an entirely different room, and the server will serve them without further checks.
  • Trigger conditions: An attacker obtains a minimal Livechat session token — for example by opening a public-facing Rocket.Chat Livechat widget — and uses that credential pair to request files from arbitrary rooms. No registered user account is required.
  • Attack vector: Fully remote and unauthenticated (AV:N/AC:L/PR:N/UI:N). File IDs (:fileId) are predictable sequential MongoDB ObjectIDs, enabling systematic enumeration of every file ever uploaded to the instance. The :name segment of the URL accepts any arbitrary value, removing a further potential barrier to exploitation.
  • Impact: Arbitrary cross-room file disclosure at scale (C:H). Livechat attachments routinely include sensitive material such as identity documents, PII-containing screenshots, and confidential support files. The CVSS Scope:Changed (S:C) metric reflects that the authorization boundary between chat rooms is violated, extending the impact well beyond the attacker’s own session context.

Affected software

  • Rocket.Chat < 8.5.1
  • Rocket.Chat < 8.4.4
  • Rocket.Chat < 8.3.6
  • Rocket.Chat < 8.2.6
  • Rocket.Chat < 8.1.6
  • Rocket.Chat < 8.0.7
  • Rocket.Chat < 7.13.9
  • Rocket.Chat < 7.10.13

Severity

CVSS 3.0 base score: 9.3 (Critical)
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Weakness: CWE-284 — Improper Access Control

Mitigation and recommended actions

  • Immediate — apply the vendor patch: Upgrade to the fixed release for your active version branch: 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, 7.13.9, or 7.10.13. The fix was delivered in GitHub PR #40889, which corrects the authorization logic in the file upload handler and Livechat room type processing.
  • If patching cannot be applied immediately: Restrict network-level access to the Rocket.Chat instance to trusted IP ranges, and consider temporarily disabling the Livechat feature to eliminate the exposed endpoint until a patch is applied.
  • Detection: Review server access logs for high-volume or sequential requests to /file-upload/ paths accompanied by Livechat session parameters (rc_room_type=l) originating from unknown or external IP addresses.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge