CVE-2026-134312: better-auth · Improper Authentication
Affects better-authSource CVE Database V5
Not known to be exploited · CVSS 7.4 High : upgrade to 1.7.16 soon.
Data as of 21 Nov 2026, 17:27 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.4 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.9 |
- Patch
- Available – fixed in 1.7.16, 1.8.0-beta.5
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/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 20 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
Fixed versions 1.7.16 and 1.8.0-beta.5 of better-auth address this authentication flaw. Users should upgrade to these or later versions to remediate the vulnerability. No additional vendor advisory indicates alternative mitigations or that the issue is already mitigated.
Description
CVE-2026-134312 is an authentication vulnerability in better-auth versions 0.4.9 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5. The flaw involves improper handling of OAuth sign-in where unverified provider emails, including those with a string "false" in the email_verified claim, are treated as verified. Additionally, mismatches in generic OAuth profile or ID-token subjects are unchecked, and Zoom provider options are ignored. This allows attackers who control an unverified email at an affected provider to sign in as the victim, link to the victim's local account, and gain session access.