Quick answers
- Is CVE-2026-55666 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55666 being exploited in the wild.
- How severe is CVE-2026-55666?
- Informational severity, with a CVSS score of 9.3, published 24 June 2026.
- Which products and versions are affected?
- Rocket.Chat < 7.10.13, 8.0.0-rc.0 - 8.0.6, 8.1.0-rc.0 - 8.1.5, 8.2.0-rc.0 - 8.2.5, 8.3.0-rc.0 - 8.3.5, 8.4.0-rc.0 - 8.4.3, 8.5.0-rc.0 - 8.5.0.
- Is there a fix for CVE-2026-55666?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-55666 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-55666?
- Check whether you run Rocket.Chat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authentication bypass vulnerability exists in Rocket.Chat's Apple OAuth implementation within 'loginHandler.ts'. The 'handleIdentityToken' function parses a JWT issued by Apple; however, if the JWT does not contain an email address, the application incorrectly falls back to an unverified email value provided directly in the login request. An attacker can exploit this by forging an Apple JWT that lacks an email claim and supplying the target victim's email address in the request body. This allows the attacker to successfully authenticate as the target user. The vulnerability is patched in versions 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13.
Affected products
- RocketChat Rocket.Chat < 7.10.13, 8.0.0-rc.0 - 8.0.6, 8.1.0-rc.0 - 8.1.5, 8.2.0-rc.0 - 8.2.5, 8.3.0-rc.0 - 8.3.5, 8.4.0-rc.0 - 8.4.3, 8.5.0-rc.0 - 8.5.0
Timeline
- 2026-06-16: advisory: GitHub advisory published by Rocket.Chat
- 2026-06-24: disclosed: CVE published to NVD