CVE-2026-67329 @better-auth/stripe before 1.6.21 Authorization Bypass via Organization Subscription

High 7.1 Published Updated

Authenticated users can bypass authorization checks to manage subscriptions and view billing details of other organizations they belong to but do not control.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-67329?

CVE-2026-67329 is a high-severity missing authorization vulnerability in better-auth stripe, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

@better-auth/stripe versions >= 1.4.11 and < 1.6.21, and >= 1.7.0-beta.0 and < 1.7.0-beta.10, contain an authorization bypass in organization subscription actions. The middleware validates the organization ID taken from the request query string against the authorizeReference callback, but the handler reads the organization ID only from the request body and falls back to the caller's active organization from their session. When these differ, an authenticated member of multiple organizations can perform subscription actions (cancel, change plan, restore, billing portal access) against an organization they belong to but should not manage, and can access another organization's billing details including payment methods, invoices, and subscription state.

Weakness: CWE-639

Which versions are affected by CVE-2026-67329?

4 open source packages ship an affected version, including @better-auth/stripe.

PackageAffectedFixed in
@better-auth/stripe npmFrom 1.4.111.6.21
@better-auth/stripe npmFrom 1.4.111.6.21
@better-auth/stripe npmFrom 1.7.0-beta.01.7.0-beta.10
@better-auth/stripe npmFrom 1.7.0-beta.01.7.0-beta.10

How do I fix CVE-2026-67329?

Upgrade @better-auth/stripe to a fixed version for your release line: 1.6.21 or 1.7.0-beta.10.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-67329 being exploited?

There is no known exploitation of CVE-2026-67329 in the wild and no public exploit code.

Sources

Also known as GHSA-h3rm-78g3-j7cp, GHSA-mp8j-p2mc-4hgv.

Is CVE-2026-67329 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free