CVE-2026-67332 @better-auth/oauth-provider before 1.7.0-beta.4 Authorization Bypass
Attackers can obtain access tokens for unauthorized resources by bypassing audience binding in the OAuth flow.
- 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-67332?
CVE-2026-67332 is a medium-severity authentication bypass vulnerability in better-auth oauth-provider, 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/oauth-provider before 1.7.0-beta.4 fails to bind access-token audience to the authorization grant, allowing clients to request tokens for unrelated resources. Attackers can complete an OAuth flow and obtain access tokens whose audience targets resource servers the authorization never covered, bypassing intended authorization boundaries.
Weakness: CWE-285
Which versions are affected by CVE-2026-67332?
2 open source packages ship an affected version, including @better-auth/oauth-provider.
| Package | Affected | Fixed in |
|---|---|---|
@better-auth/oauth-provider npm | From 1.4.8 | 1.7.0-beta.4 |
@better-auth/oauth-provider npm | From 1.4.8 | 1.7.0-beta.4 |
How do I fix CVE-2026-67332?
Upgrade @better-auth/oauth-provider to 1.7.0-beta.4 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-67332 being exploited?
There is no known exploitation of CVE-2026-67332 in the wild and no public exploit code.
Sources
Also known as GHSA-hq9c-fvm2-pfh9, GHSA-p2fr-6hmx-4528.