https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:35:37 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-05283 bdu:2026-05283 https://cve.radiocsirt.org/vuln/bdu:2026-05283 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0682 certfr-2026-avi-0682 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0682 https://cve.radiocsirt.org/vuln/euvd-2026-290302 EUVD-2026-290302 https://cve.radiocsirt.org/vuln/euvd-2026-290302 https://cve.radiocsirt.org/vuln/fkie_cve-2026-39976 <p>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&#39;s no user). The token guard then passes this value to retrieveById() without validating it&#39;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.</p> <p>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&#39;s no user). The token guard then passes this value to retrieveById() without validating it&#39;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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-39976 https://cve.radiocsirt.org/vuln/ghsa-349c-2h2f-mxf6 <p><strong>Affected:</strong> Packagist: laravel/passport</p> <p>### Impact Authentication Bypass for `client_credentials` tokens. the league/oauth2-server library sets the JWT sub claim to the client identifier (since there&#39;s no user). The token guard then passes this value to retrieveById() without validating it&#39;s actually a user identifier, potentially resolving an unrelated real user. Any machine-to-machine token can inadvertently authenticate as an actual user.</p> <p>Usage of `EnsureClientIsResourceOwner` middleware together with `Passport::$clientUuids` set to `false`, can result in resolving the user instead, as stated in the [documentation](https://laravel.com/docs/13.x/passport#:~:text=The%20underlying%20OAuth2,client%20credentials%20token).</p> <p>&gt; The [underlying OAuth2 server](https://oauth2.thephpleague.com/database-setup/#:~:text=Please%20note%20that,the%20bearer%20token.) sets the token&#39;s sub claim to the client&#39;s identifier for client credentials tokens. By default, Passport uses UUIDs for clients, so this cannot collide with a user&#39;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&#39;s ID. In such cases, using this middleware cannot guarantee that the incoming token is a client credentials token.</p> <p>### Patches Patched in v13.7.1</p> <p>### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Disallow usage of `client_credentials`.</p> <p>### References - https://github.com/laravel/pas…</p> <p><strong>Affected:</strong> Packagist: laravel/passport</p> <p>### Impact Authentication Bypass for `client_credentials` tokens. the league/oauth2-server library sets the JWT sub claim to the client identifier (since there&#39;s no user). The token guard then passes this value to retrieveById() without validating it&#39;s actually a user identifier, potentially resolving an unrelated real user. Any machine-to-machine token can inadvertently authenticate as an actual user.</p> <p>Usage of `EnsureClientIsResourceOwner` middleware together with `Passport::$clientUuids` set to `false`, can result in resolving the user instead, as stated in the [documentation](https://laravel.com/docs/13.x/passport#:~:text=The%20underlying%20OAuth2,client%20credentials%20token).</p> <p>&gt; The [underlying OAuth2 server](https://oauth2.thephpleague.com/database-setup/#:~:text=Please%20note%20that,the%20bearer%20token.) sets the token&#39;s sub claim to the client&#39;s identifier for client credentials tokens. By default, Passport uses UUIDs for clients, so this cannot collide with a user&#39;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&#39;s ID. In such cases, using this middleware cannot guarantee that the incoming token is a client credentials token.</p> <p>### Patches Patched in v13.7.1</p> <p>### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Disallow usage of `client_credentials`.</p> <p>### References - https://github.com/laravel/pas…</p> https://cve.radiocsirt.org/vuln/ghsa-349c-2h2f-mxf6