Skip to main content
Menu
CVEs

Better Auth account takeover in phone number plugin

Affects better-auth's phone number plugin from 0.4.12-beta.7 before 1.7.16, and 1.8.0-beta.0 through 1.8.0-beta.4. Fixed in 1.7.16 and 1.8.0-beta.5.

CVE-2026-134322Published November 21, 2026, updated

8.6HighCNA
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.12-beta.7 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an improper authentication vulnerability in the phone number plugin that lets sign-up and other flows save unverified phone numbers, which phone OTP sign-in then uses to select the account. Attackers can attach a victim's number to an attacker-controlled account so the victim's valid OTP sign-in yields a session for that account, exposing data the victim then enters.

Who should check

Teams running better-auth with the phone number plugin, from 0.4.12-beta.7 through 1.7.15 or 1.8.0-beta.0 through 1.8.0-beta.4, including sign-up and phone OTP sign-in flows.

Not fixed by: A strict phoneNumberValidator does not fix the shared code problem.

“You are affected if you use the phone number plugin from better-auth 0.4.12-beta.7 or later.”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Uses the better-auth phone number plugin from 0.4.12-beta.7 or later, in versions before 1.7.16 or in 1.8.0-beta.0 through 1.8.0-beta.4
  2. 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-134322 (better-auth 0.4.12-beta.7 before 1.7.16 Unverified Phone Number 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-134322 (entry last updated 2026-11-21):
Affected:
- npm package better-auth: from 0.4.12-beta.7, 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 the better-auth phone number plugin from 0.4.12-beta.7 or later, in versions before 1.7.16 or in 1.8.0-beta.0 through 1.8.0-beta.4 (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-q747-mqgr-4gh7)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-134322 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134322 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-q747-mqgr-4gh7
- https://www.vulncheck.com/advisories/better-auth-0.4.12-beta.7-before-1.7.16-unverified-phone-number-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-134322
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-134322"}.

Affected versions

cve.now Index

41Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach20/20better-auth: 19.7M downloads a week
  • Severity8.6/10CVSS 8.6
  • No patch0/5No signal

What would change the score

  • Would score about 91 if added to CISA KEV
  • Would score about 86 if CISA's SSVC rates exploitation active

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · better-auth/better-auth · Advisory GHSA-q747-mqgr-4gh7
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134322
RecordNVD · CVE-2026-134322
Other links 1
Linkvulncheck.com · advisories/better-auth-0.4.12-beta.7-before-1.7.16-unverified-phone-number-account-takeover

Questions about CVE-2026-134322

Is CVE-2026-134322 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 who saves a victim's phone number on their own account can get the victim's sign-in to open a session for the attacker's account. Data the victim enters may then become available to the attacker.

Source: github.com

Which versions are affected by CVE-2026-134322?

better-auth (npm): from 0.4.12-beta.7 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?

The issue applies to the better-auth phone number plugin from 0.4.12-beta.7 or later, in versions before 1.7.16 or in 1.8.0-beta.0 through 1.8.0-beta.4. A reader can check the installed better-auth version in the project's package.json or lockfile and whether the phone number plugin is in use.

Source: github.com

How do I fix CVE-2026-134322?

Upgrade better-auth to 1.7.16 or to 1.8.0-beta.5, depending on which release line is in use.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.