CVE-2026-67327 json
better-auth before 1.6.22 Account Takeover via Magic-Link Email-OTP
published 4mo ago modified last mo. also EUVD-2026-51841 , GHSA-qq9h-g4jm-xgf3
- cvss
- 8.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
better-auth versions >= 1.1.3 and < 1.6.22 (and pre-release versions >= 1.7.0-beta.0 and < 1.7.0-beta.10) are vulnerable to account takeover via pre-account hijacking on magic-link and email-OTP sign-in when open email/password registration is enabled. An attacker registers an account with the victim's email address and an attacker-chosen password; the account remains unverified. When the legitimate owner later signs in via the magic-link or email-OTP passwordless flow, the account is marked verified without removing the pre-existing password or revoking existing sessions, so the attacker's password remains valid, granting persistent access to the victim's account. Fixed in 1.6.22 and 1.7.0-beta.10.
Patch / fix
- npm better-auth 1.6.22, 1.7.0-beta.10
- better-auth better-auth 1.6.22, 1.7.0-beta.10
Is CVE-2026-67327 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 8.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L |
| GitHub | 3.1 | 8.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L |
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | better-auth | >=1.1.3, <1.6.22 >=1.7.0-beta.0, <1.7.0-beta.10 |
1.6.22 1.7.0-beta.10 |
Affected products
- better-auth better-auth
Classification
References
-
github.com
/better-auth/better-auth/pull/10239
web
-
github.com
/better-auth/better-auth/commit/c06a56d83a40bbaeac12d3a8b8b67e59f92a9110
web
-
github.com
/better-auth/better-auth/security/advisories/GHSA-qq9h-g4jm-xgf3
vendor-advisory, web, advisory
-
vulncheck.com
/advisories/better-auth-before-account-takeover-via-magic-link-email-otp
third-party-advisory
-
github.com
/better-auth/better-auth
package
-
github.com
/better-auth/better-auth/releases/tag/v1.6.22
web
-
github.com
/better-auth/better-auth/releases/tag/v1.7.0-beta.10
web
Sources
- CVE List CVE-2026-67327
- GitHub Advisory GHSA-qq9h-g4jm-xgf3
- NVD CVE-2026-67327
- Maintainer advisory GHSA-qq9h-g4jm-xgf3
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of better-auth/better-auth published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.