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

Back
New CVE Detected

CVE-2026-45689 – Unauthenticated OAuth2 Token Hijacking via NoSQL Injection – Rocket.Chat (prior …

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

A critical vulnerability, CVE-2026-45689, has been identified in Rocket.Chat’s built-in OAuth2 server, affecting all versions 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. The flaw is a NoSQL injection (MongoDB operator injection) in the /oauth/token endpoint that allows an unauthenticated remote attacker to obtain valid OAuth access tokens for arbitrary users — including administrators — with a single HTTP POST request. With a CVSS v3.1 base score of 9.1 (Critical), successful exploitation requires no credentials, user interaction, or prior access to the target instance.

Technical details

  • Root cause: The OAuth2 server’s grant-parameter validator coerces non-string inputs to strings for regex-based validation (causing crafted objects to pass as "[object Object]"), but then forwards the original, un-sanitized objects directly into MongoDB findOne() queries against the oauth_apps and oauth_access_tokens collections. The /oauth/token endpoint lacks the typeof type-guards present in /oauth/authorize, leaving it fully exposed.
  • Trigger conditions: The target instance must have at least one registered OAuth application and at least one refresh token persisted in the oauth_access_tokens collection (tokens persist indefinitely after initial user authorization).
  • Attack vector: An unauthenticated attacker sends a single HTTP POST to /oauth/token substituting MongoDB operator objects — e.g., {"$ne": null} — for the client_id, client_secret, and refresh_token string parameters. MongoDB matches the first available record and the server issues a fresh, valid {access_token, refresh_token} pair bound to that user. By iterating requests with $nin and $regex operators, the attacker can walk the entire oauth_access_tokens collection and harvest one fresh token per user per request.
  • Impact: Each stolen access token is a first-class bearer credential against the full /api/v1/* REST surface as the corresponding user. If any harvested token belongs to an administrator, the attacker gains complete admin API access. Admin-level API access includes the ability to install Apps-Engine applications, constituting server-side code execution on the Rocket.Chat host.

Affected software

  • Rocket.Chat all versions prior to 7.10.11
  • Rocket.Chat 7.11.x through 7.13.x prior to 7.13.7
  • Rocket.Chat 8.0.x prior to 8.0.5
  • Rocket.Chat 8.1.x prior to 8.1.4
  • Rocket.Chat 8.2.x prior to 8.2.3
  • Rocket.Chat 8.3.x prior to 8.3.3
  • Rocket.Chat 8.4.x prior to 8.4.1
  • Rocket.Chat 8.5.x prior to 8.5.0

Severity

CVSS v3.1 Base Score: 9.1 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate action — patch: Upgrade to one of the fixed releases: 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, depending on your currently deployed branch.
  • If immediate patching is not possible: Restrict network access to the Rocket.Chat /oauth/token endpoint at the perimeter (firewall or reverse proxy) to prevent unauthenticated external requests until the patch can be applied. Disabling unused OAuth applications within the admin panel reduces the attack surface but does not fully remediate the vulnerability.
  • Audit existing OAuth access tokens for anomalous activity and consider revoking all active tokens as a precautionary measure following patching.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge