p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de @better-auth/scim

Vulnérabilité publiée pour @better-auth/scim au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 3

  1. CVE-2026-67334

    Moyenne · CVSS 5.1EPSS 0,32%Correctif disponible

    better-auth Stale Sessions Persist After User Deletion

    better-auth versions before 1.6.11 fail to delete cached sessions when removing users via admin, anonymous, or SCIM endpoints when secondaryStorage is configured and storeSessionInDatabase is false. Attackers can reuse deleted user session tokens to maintain authentication for up to seven days after account deletion.

    • Mettez à jour vers 1.6.11
    Publication Mise à jour
  2. CVE-2026-67331

    Élevée · CVSS 8.7EPSS 0,39%Correctif disponible

    better-auth SCIM 1.5.0 before 1.7.0-beta.4 Authorization Bypass

    better-auth SCIM versions from 1.5.0 before 1.7.0-beta.4 fail to bind non-organization SCIM providers to their creator by default, allowing authenticated users to manage other users' providers. Attackers can regenerate SCIM bearer tokens, invalidate legitimate tokens, and authenticate to SCIM API routes with the attacker-controlled token.

    • Mettez à jour vers 1.7.0-beta.4
    Publication Mise à jour
  3. CVE-2026-67330

    Critique · CVSS 9.4EPSS 0,6%Correctif disponible

    better-auth SCIM 1.4.0-beta.27 through 1.6.21 Account Takeover via Provider-ID Collision

    @better-auth/scim (a better-auth plugin) versions >= 1.4.0-beta.27 through <= 1.6.21 and >= 1.7.0-beta.0 through <= 1.7.0-beta.9 contain an authorization bypass. SCIM token issuance did not reject provider IDs already used by existing SSO, SAML, OIDC, generic OAuth, or social account providers, and the same logical provider ID was used for both SCIM provider configuration and account ownership. An authenticated user could mint a SCIM token whose provider ID collided with an existing provider namespace, causing SCIM user routes to resolve account rows the token never provisioned. This allowed listing, reading, updating (including rewriting glo

    • Mettez à jour vers 1.6.22
    • Mettez à jour vers 1.7.0-beta.10
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →