dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-55762

HIGH · 8.1 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 →
87/100
Remediation priority · High
Remotely reachable 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, the POST /api/v1/fingerprint REST endpoint enforces authentication (authRequired: true) but performs no authorization check. Any authenticated user — including a standard user role account — can call this endpoint with {"setDeploymentAs": "new-workspace"} to permanently deregister the workspace from Rocket.Chat Cloud. This wipes all cloud credentials, removes the workspace license, breaks push notifications for all users, and requires manual re-registration to recover. 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

The POST /api/v1/fingerprint endpoint in Rocket.Chat enforces authentication but lacks authorization checks, allowing any authenticated user (including standard user accounts) to permanently deregister the workspace from Rocket.Chat Cloud by sending {"setDeploymentAs": "new-workspace"}. This destructive action wipes cloud credentials, removes the workspace license, and breaks push notifications for all users.

MitigationUpgrade Rocket.Chat to version 7.10.13, 8.0.7, 8.1.6, 8.2.6, 8.3.6, 8.4.4, or 8.5.1 or later, which contain the authorization fix for this vulnerability.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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. Identify Rocket.Chat version
    Run `rocketctl version` or check the version from the admin panel at /admin/info, or query the /api/v1/info endpoint
    Affected if 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
  2. Confirm /api/v1/fingerprint endpoint exists
    Send an authenticated GET request to /api/v1/fingerprint and verify the endpoint responds
    Affected if Endpoint returns a valid response (even with 401 if auth not provided, meaning the endpoint is exposed)
  3. Check if authentication is enforced
    Send an unauthenticated request to /api/v1/fingerprint and verify it returns 401 or requires credentials
    Affected if Authentication IS enforced (returns 401 without credentials), but authorization is NOT checked for authenticated users
  4. Verify authorization policy on fingerprint endpoint
    Use admin panel at /admin/settings/OAuth or inspect API permission settings to confirm if /api/v1/fingerprint has role-based access controls
    Affected if No role-based permission restrictions are configured for the fingerprint endpoint, allowing any authenticated user access
  5. Check workspace cloud registration status
    Navigate to /admin/cloud or query the workspace cloud settings to see if the workspace is connected to Rocket.Chat Cloud
    Affected if Workspace is currently registered with Rocket.Chat Cloud (indicating the destructive action would have impact)

You are affected if your Rocket.Chat version is before the fixed releases AND the /api/v1/fingerprint endpoint is accessible to standard users without authorization checks, especially if your workspace is connected to Rocket.Chat Cloud.

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 7.10.13, 8.0.7, 8.1.6, 8.2.6, 8.3.6, 8.4.4, or 8.5.1 or later, which contain the authorization fix for this vulnerability.

Recommended fix High confidence

Upgrade to Rocket.Chat 8.5.1 (or one of the fixed versions: 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, or 7.10.13)

  1. Identify current Rocket.Chat version by checking the running instance or deployment configuration
  2. Plan maintenance window as upgrade may require brief service restart
  3. Backup current database and configuration files before proceeding
  4. Upgrade Rocket.Chat to version 8.5.1 (or 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, or 7.10.13 depending on your release train)
  5. After upgrade, verify the POST /api/v1/fingerprint endpoint now properly enforces authorization (should require admin/owner role)
  6. Test that legitimate workspace cloud registration functionality works correctly
  7. Monitor logs for any unauthorized attempts to access this endpoint
Caveat Standard upgrade risks apply — review release notes for your version jump for any deprecation notices

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55762 — 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-55762 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