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

New CVE Detected

CVE-2026-55666 – Authentication Bypass / Account Takeover – Rocket.Chat prior to 8.5.1 / 8.4.4 / …

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

Summary

CVE-2026-55666 is a critical authentication bypass and account takeover vulnerability in Rocket.Chat’s Apple Sign-In OAuth flow, rated 9.3 (Critical) under CVSS 4.0. The flaw exists in apps/meteor/app/apple/server/loginHandler.ts, where a missing validation on an email-fallback path allows an unauthenticated attacker to forge Apple JWTs and take over arbitrary user accounts. No authentication and no user interaction are required to exploit this vulnerability.

Technical details

  • Root cause: In apps/meteor/app/apple/server/loginHandler.ts, the handleIdentityToken function parses JWTs issued by Apple during the OAuth flow and attempts to extract an email claim. When the JWT does not contain an email field, the code falls back to accepting an arbitrary email value supplied directly by the requester, with no validation. This is classified as CWE-287 (Improper Authentication) and CWE-288 (Authentication Bypass Using an Alternate Path or Channel).
  • Trigger condition: Apple Sign-In (Apple OAuth) must be enabled on the Rocket.Chat instance. The attacker crafts a forged Apple JWT that deliberately omits the email claim, then includes an arbitrary target email address in the OAuth request body.
  • Attack vector: Fully remote and unauthenticated over the network. The attacker needs only to know (or enumerate) a valid user’s email address on the target instance.
  • Impact: Complete account takeover — the attacker authenticates as any targeted user, gaining full access to that user’s messages, channels, files, and permissions. In instances where administrative accounts use Apple Sign-In, this can escalate to full platform compromise.

Affected software

  • Rocket.Chat versions prior to 7.10.13
  • Rocket.Chat versions 8.0.x prior to 8.0.7
  • Rocket.Chat versions 8.1.x prior to 8.1.6
  • Rocket.Chat versions 8.2.x prior to 8.2.6
  • Rocket.Chat versions 8.3.x prior to 8.3.6
  • Rocket.Chat versions 8.4.x prior to 8.4.4
  • Rocket.Chat versions 8.5.x prior to 8.5.1

Severity

CVSS 4.0 Base Score: 9.3 (Critical)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate action — patch: Upgrade to one of the fixed releases: 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, or 7.10.13, depending on your current release branch. Patches are available from the official Rocket.Chat release channel.
  • If patching is not immediately possible: Disable Apple Sign-In / Apple OAuth in the Rocket.Chat administration panel (Administration → OAuth → Apple) to eliminate the vulnerable code path until the upgrade can be applied.
  • General hardening: Restrict public internet access to Rocket.Chat login endpoints where not operationally required, and review OAuth provider configurations to ensure only necessary providers are enabled.

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