Description
Laravel Passport provides OAuth2 server support to Laravel. From 13.0.0 to before 13.7.1, there is an 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. This vulnerability is fixed in 13.7.1.
Affected products
laravel: passport
References5
- github.com/laravel/passport/security/advisories/GHSA-349c-2h2f-… MitigationVendor Advisory
- github.com/laravel/passport/pull/1901 Issue TrackingPatch
- github.com/laravel/passport/pull/1902 Issue TrackingPatch
- github.com/thephpleague/oauth2-server/issues/1456#issuecomment-… Issue TrackingPatch
- github.com/laravel/passport/issues/1900 ExploitIssue Tracking
Metrics
- CVSS 3.1
-
7.1
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N - EPSS — exploit probability
- 0% percentile: 22 · as of 12 November 2026
- CWE
- CWE-287
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.