Advisory

GHSA-349c-2h2f-mxf6

Also known as: CVE-2026-39976

Summary

Laravel Passport: TokenGuard Authenticates Unrelated User for Client Credentials Tokens

Details

Impact
Authentication Bypass for client_credentials tokens. the league/oauth2-server library sets the JWT sub claim to the client identifier (since there's no user). The token guard then passes this value to retrieveById() without validating it's actually a user identifier, potentially resolving an unrelated real user. Any machine-to-machine token can inadvertently authenticate as an actual user.

Usage of EnsureClientIsResourceOwner middleware together with Passport::$clientUuids set to false, can result in resolving the user instead, as stated in the documentation.

> The underlying OAuth2 server sets the token's sub claim to the client's identifier for client credentials tokens. By default, Passport uses UUIDs for clients, so this cannot collide with a user's integer primary key. However, if you have set Passport::$clientUuids to false, a client credentials token may inadvertently resolve a user whose ID matches the client's ID. In such cases, using this middleware cannot guarantee that the incoming token is a client credentials token.

Patches
Patched in v13.7.1

Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Disallow usage of client_credentials.

References

  • https://github.com/laravel/passport/issues/1900
  • https://github.com/laravel/passport/pull/1901
  • https://github.com/laravel/passport/pull/1902
  • https://github.com/thephpleague/oauth2-server/issues/1456#issuecomment-2734989996

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-04-08 19:57 UTC
Modified
2026-04-13 18:11 UTC

Affected packages and fixes

laravel/passport

Packagist · All systems

Affected

  • introduced 13.0.0, fixed 13.7.1 (ecosystem)

Fixed versions

13.7.1

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences