Better Auth privilege escalation in organization invitations
- 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.5.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a privilege escalation vulnerability in the organization plugin, where the creator role check compares the raw invitation role string while later checks trim it. Admins or other non-creator roles that can invite can submit a padded role such as " owner" that becomes owner on acceptance, allowing deletion of the organization and removal of original owners.
Who should check
Teams running better-auth's organization plugin (versions 1.5.5 to before 1.7.16, or 1.8.0-beta.0 to before 1.8.0-beta.5) where non-creator roles such as admins can send invitations.
“You are affected if you use the organization plugin from better-auth 1.5.5 or later, and a role other than the creator role can create invitations.”
What to do
Check whether your setup matches what the bug needs.
better-auth organization plugin, versions 1.5.5 up to 1.7.16, or 1.8.0-beta.0 up to 1.8.0-beta.5 A role other than the creator role can create invitationsUpgrade 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-134318 (better-auth 1.5.5 before 1.7.16 Privilege Escalation via Padded Invitation Role), 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-134318 (entry last updated 2026-11-21):
Affected:
- npm package better-auth: from 1.5.5, 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 organization plugin, versions 1.5.5 up to 1.7.16, or 1.8.0-beta.0 up to 1.8.0-beta.5 (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-c85h-5mrr-mgx4)
- A role other than the creator role can create invitations (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-c85h-5mrr-mgx4)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-134318 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134318 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-c85h-5mrr-mgx4
- https://www.vulncheck.com/advisories/better-auth-1.5.5-before-1.7.16-privilege-escalation-via-padded-invitation-role
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-134318
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-134318"}.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
- Severity6.9/10CVSS 6.9
- 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-c85h-5mrr-mgx4 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134318 |
| Record | NVD · CVE-2026-134318 |
| Other links 1 | |
| Link | vulncheck.com · advisories/better-auth-1.5.5-before-1.7.16-privilege-escalation-via-padded-invitation-role |
Questions about CVE-2026-134318
Is CVE-2026-134318 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 role other than the creator role can create invitations that produce an owner account in the same organization. That owner can then delete the organization and remove the original owners.
Source: github.com
Which versions are affected by CVE-2026-134318?
better-auth (npm): from 1.5.5 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 organization plugin of better-auth from 1.5.5 up to 1.7.16, and from 1.8.0-beta.0 up to 1.8.0-beta.5. To check, look at the better-auth version in the project's dependencies and whether the organization plugin is in use.
Source: github.com
How do I fix CVE-2026-134318?
Upgrade better-auth to 1.7.16 or later on the 1.7 line, or to 1.8.0-beta.5 or later on the 1.8 beta line. No vendor patch ids are given.
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.