Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. @better-auth/oauth-provider
  4. ›
  5. GHSA-p2fr-6hmx-4528

GHSA-p2fr-6hmx-4528: @better-auth/oauth-provider may provide access tokens for unauthorized audiences via unbound resource indicators

July 7, 2026

@better-auth/oauth-provider lets an OAuth client choose the access-token audience through the RFC 8707 resource parameter at the token endpoint. It does not bind that choice to the authorization grant. A client that completes a normal authorization flow can request a JWT access token whose audience targets a resource server the authorization never covered. The only constraint is that the resource appears in the server’s validAudiences allowlist. The same gap applies to the refresh grant: a refresh token issued in a flow targeting one resource can be redeemed for an access token bound to a different allow-listed resource.

References

  • github.com/advisories/GHSA-p2fr-6hmx-4528
  • github.com/better-auth/better-auth/releases/tag/v1.7.0-beta.4
  • github.com/better-auth/better-auth/security/advisories/GHSA-p2fr-6hmx-4528

Code Behaviors & Features

Detect and mitigate GHSA-p2fr-6hmx-4528 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions starting from 1.4.8 before 1.7.0-beta.4

Fixed versions

  • 1.7.0-beta.4

Solution

Upgrade to version 1.7.0-beta.4 or above.

Impact 6.4 MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Learn more about CVSS

Weakness

  • CWE-285: Improper Authorization
  • CWE-863: Incorrect Authorization

Source file

npm/@better-auth/oauth-provider/GHSA-p2fr-6hmx-4528.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sat, 11 Jul 2026 00:17:04 +0000.