Better Auth privilege escalation via admin plugin update-user endpoint
- Exploited
- No known exploitation
- Fix
- Fixed in 1.7.16, 1.8.0-beta.5
- Who is exposed
- Specific setups only
Summary
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.
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
“You use the admin plugin and the phone number plugin from better-auth”
What to do
Check whether your setup matches what the bug needs.
better-auth versions 1.3.0 up to 1.7.16, and 1.8.0-beta.0 up to 1.8.0-beta.5 The admin plugin and the phone number plugin from better-auth are in use A role other than the full admin role holds the user:update permissionUpgrade 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-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"}.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.6/10CVSS 7.6
- No patch0/5No signal
What would change the score
- Would score about 86 if added to CISA KEV
- Would score about 81 if CISA's SSVC rates exploitation active
- Would score about 43 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-g95c-wqvr-8c3j |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134311 |
| Record | NVD · CVE-2026-134311 |
| Other links 1 | |
| Link | vulncheck.com · advisories/better-auth-1.3.0-before-1.7.16-privilege-escalation-via-admin-update-user-phone-number |
Questions about CVE-2026-134311
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: cve.now feed data
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: vulncheck.com, github.com
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: cve.now feed data
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: vulncheck.com, github.com
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: vulncheck.com, 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.