Skip to content

Vendor

better-auth vulnerabilities

34 published CVES affecting better-auth, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
34
Critical
7
High
18
Medium
6
Low
3
Unscored
0
CISA KEV
0
Atom feed of better-auth alerts

Products

Latest better-auth CVEs

Newest publication first · page 1 of 2

  1. CriticalCVSS 9.1 EPSS 0.20%

    @better-auth/expo before 1.7.16 allows certain account-takeover outcomes (e.g., unauthenticated changes of any account's email address), because it signs a caller-supplied state value without checking whether that value had been issued by the server. NOTE: the application secret...

  2. HighCVSS 7.1 EPSS 0.35%

    better-auth passkey versions before 1.4.0 contain an insecure direct object reference vulnerability in the passkey deletion endpoint that allows authenticated users to delete arbitrary passkeys by ID. Attackers with valid sessions can submit crafted requests to the delete-passkey...

  3. MediumCVSS 5.1 EPSS 0.32%

    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...

  4. HighCVSS 8.7 EPSS 0.39%

    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 authent...

  5. HighCVSS 8.6 EPSS 0.49%

    @better-auth/sso versions before 1.6.21 contain multiple authentication bypass vulnerabilities in SSO provider handling that allow attackers to sign in as arbitrary users. Attackers can exploit domain verification parsing mismatches, orphaned provider accounts, unbound SAML asser...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.