CVE-2026-39976
Laravel Passport provides OAuth2 server support to Laravel. From …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/laravel/passport/issues/1900
- github.com/laravel/passport/pull/1901
- github.com/laravel/passport/pull/1902
- github.com/laravel/passport/security/advisories/GHSA-349c-2h2f-mxf6
- github.com/thephpleague/oauth2-server/issues/1456#issuecomment-2734989996
- nvd.nist.gov/vuln/detail/CVE-2026-39976
- github.com/advisories/GHSA-349c-2h2f-mxf6
- nvd.nist.gov/vuln/detail/CVE-2026-39976
- cve.org/CVERecord?id=CVE-2026-39976
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.