Skip to main content
CVE-2026-134318VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134318· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.7.16 when convenient.

Data as of 21 Nov 2026, 19:58 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.14.9
Patch
Available – fixed in 1.7.16, 1.8.0-beta.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade better-auth to 1.7.16; better-auth to 1.8.0-beta.5; better-auth to 1.8.0-beta.5 or 1.7.16.

Affected software

ProductAffectedFixed in
better-authbetter-authAffected
  • >=1.5.5 <1.7.16
Fixed in
  • 1.7.16
better-authbetter-authAffected
  • >=1.8.0-beta.0 <1.8.0-beta.5
Fixed in
  • 1.8.0-beta.5
npmbetter-authpkg:npm/better-authOther threatsAffected
  • >=1.5.5 <1.7.16
  • >=1.8.0-beta.0 <1.8.0-beta.5
Fixed in
  • 1.7.16
  • 1.8.0-beta.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict invite permissions to trusted users only to reduce risk.

Description

better-auth versions 1.5.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contain a privilege escalation vulnerability in the organization plugin. The flaw arises because the creator role check compares the raw invitation role string, while subsequent checks trim whitespace. This allows an attacker with invite permissions to submit a padded role string (e.g., " owner") that is accepted as an owner role upon invitation acceptance. Exploitation can lead to deletion of the organization and removal of original owners.

References

Community reviews

Loading reviews…