Skip to main content
CVE-2026-134317VulnerabilityPublished

@better-auth/stripe 1.2.0-beta.18 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an authorization bypass

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134317· Medium 6.0

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

Data as of 21 Nov 2026, 19:58 UTC

CVSS 4.0 base score
6.0Medium
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.0
CNA (VulnCheck)CVSS 3.15.9
Patch
Available – fixed in 1.7.16, 1.8.0-beta.5
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/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 stripe to 1.7.16; stripe to 1.8.0-beta.5; stripe to 1.8.0-beta.5 or 1.7.16.

Affected software

ProductAffectedFixed in
better-authstripeAffected
  • >=1.2.0-beta.18 <1.7.16
Fixed in
  • 1.7.16
better-authstripeAffected
  • >=1.8.0-beta.0 <1.8.0-beta.5
Fixed in
  • 1.8.0-beta.5
npmstripepkg:npm/stripeOther threatsAffected
  • >=1.2.0-beta.18 <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 access to the stripeCustomerId field in sign-up and update-user requests to prevent unauthorized modification. Implement strict authorization checks to ensure users can only modify their own Stripe customer ID.

Description

@better-auth/stripe versions 1.2.0-beta.18 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contain an authorization bypass vulnerability. This flaw allows users to replace their Stripe customer ID with another customer's ID via sign-up or update-user requests. Exploitation enables attackers who know another customer's Stripe ID to access that customer's billing portal, view invoices and billing details, change payment methods, and modify or cancel subscriptions.

References

Community reviews

Loading reviews…