Skip to main content
Menu
CVEs

Better Auth Stripe authorization bypass via stripeCustomerId mass assignment

Affects @better-auth/stripe from 1.2.0-beta.18 to before 1.7.16 and 1.8.0-beta.0 to before 1.8.0-beta.5 when the stripe() plugin is registered. Fixed in 1.7.16 and 1.8.0-beta.5.

CVE-2026-134317Published November 21, 2026, updated

6.0MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.7.16, 1.8.0-beta.5
Who is exposed
Specific setups only

Summary

Written by a model

@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.

Who should check

Teams running @better-auth/stripe with the stripe() plugin and subscriptions enabled, on 1.2.0-beta.18 up to 1.7.16, or 1.8.0-beta.0 up to 1.8.0-beta.5.

Not fixed by: Upgrading alone does not fix customer IDs already written; check for duplicates.

“You are affected if you register the stripe() plugin from @better-auth/stripe 1.2.0-beta.18 or later.”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Registers the stripe() plugin from @better-auth/stripe 1.2.0-beta.18 or later Billing effects require subscription.enabled set to true
  2. Upgrade 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-134317 (@better-auth/stripe before 1.7.16 Authorization Bypass via stripeCustomerId Mass Assignment), 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-134317 (entry last updated 2026-11-21):
Affected:
- npm package @better-auth/stripe: from 1.2.0-beta.18, fixed in 1.7.16
- npm package @better-auth/stripe: 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):
- Registers the stripe() plugin from @better-auth/stripe 1.2.0-beta.18 or later (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-x8j7-xh58-rv6x)
- Billing effects require subscription.enabled set to true (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-x8j7-xh58-rv6x)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134317 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134317 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-x8j7-xh58-rv6x
- https://www.vulncheck.com/advisories/better-auth-stripe-before-1.7.16-authorization-bypass-via-stripecustomerid-mass-assignment
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-134317
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-134317"}.

Affected versions

cve.now Index

26Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach12/20@better-auth/stripe: 462.4K downloads a week
  • Severity6/10CVSS 6.0
  • No patch0/5No signal

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 33 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · better-auth/better-auth · Advisory GHSA-x8j7-xh58-rv6x
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134317
RecordNVD · CVE-2026-134317
Other links 1
Linkvulncheck.com · advisories/better-auth-stripe-before-1.7.16-authorization-bypass-via-stripecustomerid-mass-assignment

Questions about CVE-2026-134317

Is CVE-2026-134317 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 flaw in how the stripeCustomerId field is mass-assigned lets a signed-in user open another customer's billing portal. From there they can see invoices and billing details, change payment methods, and cancel or change subscriptions.

Source: github.com

Which versions are affected by CVE-2026-134317?

@better-auth/stripe (npm): from 1.2.0-beta.18 before 1.7.16. @better-auth/stripe (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 from 1.2.0-beta.18 up to but not including 1.7.16, and 1.8.0-beta.0 up to but not including 1.8.0-beta.5, are in range. Check the installed @better-auth/stripe version in your package manifest or lockfile, and check whether the stripe() plugin is registered. The billing effects also require subscription.enabled set to true.

Source: github.com

How do I fix CVE-2026-134317?

Upgrade @better-auth/stripe to 1.7.16 or to 1.8.0-beta.5, depending on which release line you use.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.