CVE-2026-134315: 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:15 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.4 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 6.4 |
- Patch
- Available – fixed in 1.7.16, 1.8.0-beta.5
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/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 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
Upgrade better-auth to version 1.7.16 or later, or 1.8.0-beta.5 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
Description
better-auth versions 1.4.0 up to but not including 1.7.16, and 1.8.0-beta.0 up to but not including 1.8.0-beta.5, contain an improper authentication vulnerability. The flaw arises because email-change links record the old and new email addresses but do not record the requesting user. This allows an attacker to reuse a valid email-change link issued for their own account after a victim registers the attacker's old email address, enabling the attacker to gain a session and change the victim's email to one they control. The issue is fixed in versions 1.7.16 and 1.8.0-beta.5.