Skip to content

Commit a71812c

Browse files
1 parent 3a77ba4 commit a71812c

1 file changed

Lines changed: 10 additions & 4 deletions

File tree

advisories/github-reviewed/2026/04/GHSA-349c-2h2f-mxf6/GHSA-349c-2h2f-mxf6.json

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,11 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-349c-2h2f-mxf6",
4-
"modified": "2026-04-08T19:57:55Z",
4+
"modified": "2026-04-13T17:48:46Z",
55
"published": "2026-04-08T19:57:55Z",
6-
"aliases": [],
6+
"aliases": [
7+
"CVE-2026-39976"
8+
],
79
"summary": "Laravel Passport: TokenGuard Authenticates Unrelated User for Client Credentials Tokens",
810
"details": "### Impact\nAuthentication 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.\n\n\nUsage 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). \n\n> The [underlying OAuth2 server](https://oauth2.thephpleague.com/database-setup/#:~:text=Please%20note%20that,the%20bearer%20token.) 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.\n\n### Patches\nPatched in v13.7.1\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\nDisallow usage of `client_credentials`. \n\n\n### References\n- https://github.com/laravel/passport/issues/1900\n- https://github.com/laravel/passport/pull/1901\n- https://github.com/laravel/passport/pull/1902\n- https://github.com/thephpleague/oauth2-server/issues/1456#issuecomment-2734989996",
911
"severity": [
@@ -23,7 +25,7 @@
2325
"type": "ECOSYSTEM",
2426
"events": [
2527
{
26-
"introduced": "0"
28+
"introduced": "13.0.0"
2729
},
2830
{
2931
"fixed": "13.7.1"
@@ -38,6 +40,10 @@
3840
"type": "WEB",
3941
"url": "https://github.com/laravel/passport/security/advisories/GHSA-349c-2h2f-mxf6"
4042
},
43+
{
44+
"type": "ADVISORY",
45+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-39976"
46+
},
4147
{
4248
"type": "WEB",
4349
"url": "https://github.com/laravel/passport/issues/1900"
@@ -66,6 +72,6 @@
6672
"severity": "HIGH",
6773
"github_reviewed": true,
6874
"github_reviewed_at": "2026-04-08T19:57:55Z",
69-
"nvd_published_at": null
75+
"nvd_published_at": "2026-04-09T17:16:31Z"
7076
}
7177
}

0 commit comments

Comments
 (0)