dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-58066

CRITICAL · 9.8 CVSS v3.0 Published 2026-07-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 3 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's SAML SSO before versions 8.7.0, 8.6.1, 8.5.2, 8.4.5, 8.3.7, 8.2.7, 8.1.7, 8.0.8, and 7.10.14 verified XML signatures but did not bind the validated signature to samlp:Response / saml:Assertion. An attacker could submit a wrapped document carrying forged identity attributes alongside any valid signature made by the trusted IdP certificate, and log in as an arbitrary user.

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 SAML SSO verifies XML signatures but fails to cryptographically bind the validated signature to the samlp:Response or saml:Assertion elements. This enables XML Signature Wrapping (XSW) attacks where attackers can inject forged identity attributes into a SAML response while carrying a valid signature from the trusted IdP, allowing authentication as any user.

MitigationUpgrade to version 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, 8.6.1, or 8.7.0 or later, which implement proper signature-to-element binding to prevent XSW attacks.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 installation and version
    Run 'rocketchat/serverinfo' via admin API, check package.json in installation directory, or query the /api/info endpoint
    Affected if The installed version is any release prior to 7.10.14, or any 8.x release prior to 8.7.0 (including 8.6.1, 8.5.2, 8.4.5, 8.3.7, 8.2.7, 8.1.7, or 8.0.8)
  2. Determine if SAML SSO is enabled
    Log into Rocket.Chat as administrator, navigate to Administration > Settings > SAML, or query the 'saml' configuration via the API at /api/v1/settings
    Affected if SAML login is configured and enabled for one or more workspace logins
  3. Confirm SAML service provider is configured
    Check the SAML configuration for entries under 'SAML Enterprise' section, specifically verify that a Service Provider (SP) entity is defined with X.509 certificate settings
    Affected if A SAML service provider entry exists with certificate and issuer settings configured
  4. Check SAML signature validation settings
    Review the SAML settings in Administration > Settings > SAML for 'Signature Validation' or 'Validate XML Signatures' options, if accessible
    Affected if XML signature validation is enabled but the configuration does not explicitly bind signatures to response/assertion content

A user is affected if they run a Rocket.Chat version prior to the fixed releases AND have SAML SSO authentication enabled with a configured service provider.

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 to version 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, 8.6.1, or 8.7.0 or later, which implement proper signature-to-element binding to prevent XSW attacks.

Recommended fix High confidence

Rocket.Chat 8.7.0 or later (latest stable release)

  1. 1. Back up your Rocket.Chat instance database and configuration files before proceeding
  2. 2. Stop the Rocket.Chat service
  3. 3. Upgrade to Rocket.Chat version 8.7.0 or later (or the latest stable release)
  4. 4. Verify the upgrade completed successfully
  5. 5. Restart the Rocket.Chat service
  6. 6. Test SAML SSO authentication to confirm the fix is working
Caveat Review release notes for any breaking changes between your current version and 8.7.0

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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