Better Auth account takeover in OAuth sign-in via unverified emails
Affects better-auth 0.4.9 through 1.7.16 and 1.8.0-beta.0 through 1.8.0-beta.5 when OAuth sign-in is used with certain providers. 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 0.4.9 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an OAuth sign-in authentication flaw that treats unverified provider emails as verified, including string "false" email_verified claims, unchecked generic OAuth profile/ID-token subject mismatches, and ignored Zoom provider options. Attackers holding a victim's address unverified at an affected provider can sign in, link to the victim's local account, and obtain its session.
Who should check
Teams running better-auth from 0.4.9 up to 1.7.16 (or 1.8.0 beta before beta.5) that use OAuth sign-in, including genericOAuth with JWKS or the Zoom provider.
“You are affected if you use OAuth sign-in from better-auth 0.4.9 or later”
What to do
Check whether your setup matches what the bug needs.
Uses OAuth sign-in from better-auth 0.4.9 or later Provider sends email_verified as a string and lets its users keep an unverified address Uses genericOAuth() with a provider that has a JWKS endpoint Uses the Zoom provider with disableSignUp, requireEmailVerification, or overrideUserInfoOnSignInUpgrade 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-134312 (Better Auth 0.4.9 before 1.7.16 OAuth Unverified Email Account Takeover), 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-134312 (entry last updated 2026-11-21):
Affected:
- npm package better-auth: from 0.4.9, 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):
- Uses OAuth sign-in from better-auth 0.4.9 or later (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-9hm7-xhfp-cx58)
- Provider sends email_verified as a string and lets its users keep an unverified address (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-9hm7-xhfp-cx58)
- Uses genericOAuth() with a provider that has a JWKS endpoint (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-9hm7-xhfp-cx58)
- Uses the Zoom provider with disableSignUp, requireEmailVerification, or overrideUserInfoOnSignIn (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-9hm7-xhfp-cx58)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-134312 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134312 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-9hm7-xhfp-cx58
- https://www.vulncheck.com/advisories/better-auth-0.4.9-before-1.7.16-oauth-unverified-email-account-takeover
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-134312
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-134312"}.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-9hm7-xhfp-cx58 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134312 |
| Record | NVD · CVE-2026-134312 |
| Other links 1 | |
| Link | vulncheck.com · advisories/better-auth-0.4.9-before-1.7.16-oauth-unverified-email-account-takeover |
Questions about CVE-2026-134312
Is CVE-2026-134312 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?
Someone who holds another person's email address unverified at an affected OAuth provider can sign in and be linked to the local account that owns that address, receiving a session for it.
Source: github.com
Which versions are affected by CVE-2026-134312?
better-auth (npm): from 0.4.9 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 versions are better-auth 0.4.9 up to the fixed releases, and the exposure depends on the setup: a provider that sends email_verified as a string and lets users keep unverified addresses, genericOAuth() with a provider that has a JWKS endpoint, or the Zoom provider with disableSignUp, requireEmailVerification, or overrideUserInfoOnSignIn. Check the better-auth version in your dependency lockfile and whether these providers or options are configured.
Source: github.com
How do I fix CVE-2026-134312?
Upgrade to better-auth 1.7.16 on the 1.7 line or 1.8.0-beta.5 on the 1.8 beta line.
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.