Better Auth account takeover via email-change links
Affects better-auth 1.4.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 with user.changeEmail enabled and email verification configured. Fixed in 1.7.16 and 1.8.0-beta.5.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.7.16, 1.8.0-beta.5
- Who is exposed
- Specific setups only
Summary
Written by a model
better-auth 1.4.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an improper authentication vulnerability because email-change links record the old and new addresses but not the requesting user. Attackers can open a still-valid link issued for their own account after a victim registers the attacker's released old address, gaining a session and changing the victim's email to one they control.
Who should check
Teams running better-auth 1.4.0 or later before 1.7.16, or 1.8.0-beta.0 before 1.8.0-beta.5, with user email changes and email verification enabled.
Not fixed by: Lowering emailVerification.expiresIn does not stop the attack.
“You are affected if you use better-auth 1.4.0 or later with all of these:”
What to do
Check whether your setup matches what the bug needs.
user.changeEmail.enabled is turned on. emailVerification.sendVerificationEmail is configured. A previous owner's released address can be registered by a new user.Upgrade to a fixed version: 1.7.16, 1.8.0-beta.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134315 (better-auth 1.4.0 before 1.7.16 Account Takeover via Email-Change Links), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134315 (entry last updated 2026-11-21):
Affected:
- npm package better-auth: from 1.4.0, fixed in 1.7.16
- npm package better-auth: from 1.8.0-beta.0, fixed in 1.8.0-beta.5
Fixed versions: 1.7.16, 1.8.0-beta.5.
Conditions (all must be true for the bug to be hit):
- user.changeEmail.enabled is turned on. (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-hwq2-v29r-p69r)
- emailVerification.sendVerificationEmail is configured. (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-hwq2-v29r-p69r)
- A previous owner's released address can be registered by a new user. (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-hwq2-v29r-p69r)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-134315 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134315 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/better-auth/better-auth/security/advisories/GHSA-hwq2-v29r-p69r
- https://www.vulncheck.com/advisories/better-auth-1.4.0-before-1.7.16-account-takeover-via-email-change-links
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134315
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134315"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach20/20better-auth: 19.7M downloads a week
- Severity7.4/10CVSS 7.4
- No patch0/5No signal
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 42 if CISA's SSVC rates it automatable
Impact
- Widely usedbetter-auth has 19.7m weekly downloads. npmjs.com
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · better-auth/better-auth · Advisory GHSA-hwq2-v29r-p69r |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134315 |
| Record | NVD · CVE-2026-134315 |
| Other links 1 | |
| Link | vulncheck.com · advisories/better-auth-1.4.0-before-1.7.16-account-takeover-via-email-change-links |
Questions about CVE-2026-134315
Is CVE-2026-134315 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
An attacker can get a session for another user's account and change that account's email to an address they control. The bug arises when a new user can register an address after its previous owner has moved to another one.
Source: github.com
Which versions are affected by CVE-2026-134315?
better-auth (npm): from 1.4.0 before 1.7.16. better-auth (npm): from 1.8.0-beta.0 before 1.8.0-beta.5.
Source: cve.now feed data
Am I affected, and how do I check?
Affected are better-auth 1.4.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, when user.changeEmail.enabled is turned on and emailVerification.sendVerificationEmail is configured. To check the setup, look at the installed better-auth version and at the user.changeEmail.enabled and emailVerification.sendVerificationEmail settings in the auth configuration.
Source: github.com
How do I fix CVE-2026-134315?
Upgrade better-auth to 1.7.16 or 1.8.0-beta.5, depending on which release line is in use.
Source: github.com
Related
- CVE-2026-67336better-auth before 1.6.11 Insecure Cryptographic Defaults via oidcProvider
- CVE-2026-110862Better Auth 1.4.0-beta.18 before 1.7.7 Authentication Bypass via Magic Link
- CVE-2025-71401better-auth before 1.4.2 basePath Modification DoS
- CVE-2026-114607better-auth: OAuth state can be used as a Magic Link to sign in as another user
- CVE-2026-110864Better Auth 1.5.0-beta.12 before 1.7.7 Authentication Bypass via OAuth Proxy
- CVE-2025-71399Better Auth before 1.4.5 Path Normalization Bypass via rou3
No corrections so far. Something wrong on this page? Report an error.