CVE-2026-55759
Received Received - Intake
Apple Sign-In JWT Replay in Rocket.Chat

Publication date: 2026-06-24

Last updated on: 2026-06-24

Assigner: GitHub, Inc.

Description
Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13, Rocket.Chat's Apple Sign-In handler verifies JWT signatures but skips claims validation. Any Apple-signed JWT with a non-empty iss is accepted regardless of aud, exp, nbf, or nonce. An attacker who obtains a target user's Apple identity token (from server logs, an intercepted sign-in flow, or another application sharing the same Apple developer team) can replay it to authenticate as that user, with no expiration on the replay window. This vulnerability is fixed in 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-24
Last Modified
2026-06-24
Generated
2026-06-25
AI Q&A
2026-06-25
EPSS Evaluated
N/A
NVD
Affected Vendors & Products
Showing 7 associated CPEs
Vendor Product Version / Range
rocket.chat rocket.chat to 8.5.1 (exc)
rocket.chat rocket.chat to 8.4.4 (exc)
rocket.chat rocket.chat to 8.3.6 (exc)
rocket.chat rocket.chat to 8.2.6 (exc)
rocket.chat rocket.chat to 8.1.6 (exc)
rocket.chat rocket.chat to 8.0.7 (exc)
rocket.chat rocket.chat to 7.10.13 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-287 When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
CWE-294 A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in Rocket.Chat's Apple Sign-In handler prior to versions 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13. The handler verifies JWT signatures but fails to validate the claims within the token. Specifically, any Apple-signed JWT with a non-empty issuer (iss) claim is accepted regardless of other important claims such as audience (aud), expiration time (exp), not before (nbf), or nonce.

An attacker who obtains a target user's Apple identity tokenβ€”possibly from server logs, intercepted sign-in flows, or another application sharing the same Apple developer teamβ€”can replay this token to authenticate as that user. This replay attack has no expiration window, meaning the attacker can reuse the token indefinitely.

Impact Analysis

This vulnerability allows an attacker to impersonate a legitimate user by replaying their Apple identity token without expiration. This can lead to unauthorized access to the user's account and potentially sensitive information within Rocket.Chat.

Because the attacker can authenticate as the user indefinitely, it poses a significant security risk including data exposure, unauthorized actions performed in the user's name, and potential compromise of communications.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade Rocket.Chat to one of the fixed versions: 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, or 7.10.13.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-55759. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart