dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-55759

HIGH · 7.4 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Rocket.Chat's Apple Sign-In handler verifies JWT signatures but fails to validate critical claims (audience, expiration, not-before, nonce). This allows attackers with a valid Apple identity token to replay it indefinitely for authentication, as tokens never expire and claims like aud are not checked.

MitigationUpgrade Rocket.Chat to version 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, or 7.10.13 or later which includes proper JWT claims validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Rocket.Chat installation
    Identify where Rocket.Chat is installed; common locations include /opt/Rocket.Chat, /var/www/rocketchat, or as a Docker container. Check running processes for 'rocketchat' or look for the service definition.
    Affected if Rocket.Chat is installed on the system
  2. Determine Rocket.Chat version
    Run 'rocketchatctl version' if available, or check the version file in the installation directory (often in package.json or a VERSION file), or query the API endpoint /api/info
    Affected if The installed version is earlier than 7.10.13, 8.0.7, 8.1.6, 8.2.6, 8.3.6, 8.4.4, or 8.5.1
  3. Check if Apple Sign-In is enabled
    Inspect Rocket.Chat configuration files (typically in /etc/rocketchat or environment variables) for OAuth or Apple-related settings; look for keys containing 'OAUTH_APPLE', 'APPLE_CLIENT_ID', or check the admin panel OAuth configuration if accessible
    Affected if Apple Sign-In / OAuth with Apple is configured and enabled in the Rocket.Chat instance

The environment is affected if Rocket.Chat version is vulnerable (before the fixed releases) AND Apple Sign-In is currently enabled as an authentication method.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Rocket.Chat to version 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, or 7.10.13 or later which includes proper JWT claims validation.

Recommended fix High confidence

8.5.1 (or latest 8.x release); 7.10.13 for 7.x branches

  1. Identify current Rocket.Chat version by checking the deployed application
  2. Determine which version branch you're running (7.x or 8.x)
  3. For 7.x branch: Upgrade to version 7.10.13 or later
  4. For 8.0.x branch: Upgrade to version 8.0.7 or later
  5. For 8.1.x branch: Upgrade to version 8.1.6 or later
  6. For 8.2.x branch: Upgrade to version 8.2.6 or later
  7. For 8.3.x branch: Upgrade to version 8.3.6 or later
  8. For 8.4.x branch: Upgrade to version 8.4.4 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55759 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data