CVE-2026-134317
Received Received - Intake

Authorization Bypass in Better Auth Stripe Integration

Vulnerability report for CVE-2026-134317, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
better-auth stripe to 1.7.16 (exc)
better-auth stripe From 1.8.0-beta.0 (inc) to 1.8.0-beta.5 (exc)
better-auth stripe 1.7.16
better-auth stripe 1.8.0-beta.5
better-auth stripe to 1.7.16|end_excluding=1.8.0-beta.0|end_excluding=1.8.0-beta.5 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-134317 is an authorization bypass vulnerability in the @better-auth/stripe package. It allows attackers to replace their own Stripe customer ID with another user's during sign-up or update requests. This grants unauthorized access to billing details, payment methods, and subscription modifications of the targeted customer.

Detection Guidance

To detect this vulnerability, check if your @better-auth/stripe package versions are below 1.7.16 or between 1.8.0-beta.0 and 1.8.0-beta.5. Review user records for duplicate or manipulated Stripe customer IDs. Audit API logs for unauthorized billing portal access attempts.

Impact Analysis

If exploited, this vulnerability could let attackers view invoices, change payment methods, or cancel subscriptions of other users. It does not expose Stripe API keys or allow direct account takeover but enables unauthorized access to sensitive billing data.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive billing and payment data, which may violate compliance requirements under GDPR (data protection) and HIPAA (protected health information). Unauthorized access to customer data could result in data breaches, triggering mandatory breach notifications and potential fines.

Mitigation Strategies

Update @better-auth/stripe to version 1.7.16 or later, or 1.8.0-beta.5 or later. Implement database hooks to strip stripeCustomerId from incoming user requests. Audit existing customer IDs for duplicates to identify potential unauthorized access.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-134317. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...