better-auth 0.4.12-beta.7 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an improper authentication
Source GCVE Database
Not known to be exploited · CVSS 8.6 High : upgrade to 1.7.16 soon.
Data as of 21 Nov 2026, 19:42 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.6 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 8.1 |
- Patch
- Available – fixed in 1.7.16, 1.8.0-beta.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade better-auth to 1.7.16; better-auth to 1.8.0-beta.5; better-auth to 1.8.0-beta.5 or 1.7.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| better-authbetter-auth | Affected
| Fixed in
|
| better-authbetter-auth | Affected
| Fixed in
|
npmbetter-authpkg:npm/better-authOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, avoid using vulnerable versions or disable the phone number plugin's sign-up and OTP sign-in flows if possible.
Description
An improper authentication vulnerability exists in better-auth versions 0.4.12-beta.7 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 in the phone number plugin. This flaw allows sign-up and other flows to save unverified phone numbers, which are then used by phone OTP sign-in to select accounts. An attacker can exploit this by associating a victim's phone number with an attacker-controlled account, causing the victim's valid OTP sign-in to yield a session for the attacker's account and potentially exposing data the victim enters.