CVE-2026-134317
@better-auth/stripe before 1.7.16 Authorization Bypass via stripeCustomerId Mass Assignment
Description
@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 vulnerability because the stripeCustomerId user field accepts values from sign-up and update-user requests, letting a user replace their own Stripe customer ID with another customer's. Attackers who know another customer's Stripe ID can open that customer's billing portal to view invoices and billing details, change payment methods, and cancel or modify subscriptions.
INFO
Published Date :
Nov. 21, 2026, 4:34 p.m.
Last Modified :
Nov. 21, 2026, 4:34 p.m.
Remotely Exploit :
Yes !
Source :
VulnCheck
Affected Products
The following products are affected by CVE-2026-134317
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | 83251b91-4cc7-4094-a5c7-464a1b83ea10 | ||||
| CVSS 3.1 | MEDIUM | MITRE-CVE | ||||
| CVSS 4.0 | MEDIUM | 83251b91-4cc7-4094-a5c7-464a1b83ea10 |
Solution
- Update @better-auth/stripe to version 1.7.16 or later.
- Update @better-auth/stripe to version 1.8.0-beta.5 or later.
- Validate that the stripeCustomerId field is properly secured.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-134317 vulnerability anywhere in the article.