Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-349c-2h2f-mxf6 | Laravel Passport: TokenGuard Authenticates Unrelated User for Client Credentials Tokens |
Fri, 10 Apr 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Laravel
Laravel passport |
|
| Vendors & Products |
Laravel
Laravel passport |
Fri, 10 Apr 2026 04:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 09 Apr 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Laravel Passport's TokenGuard Authenticates Unrelated User for Client Credentials Tokens | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-09T19:31:53.801Z
Reserved: 2026-04-08T00:01:47.628Z
Link: CVE-2026-39976
Updated: 2026-04-09T17:38:05.372Z
Status : Awaiting Analysis
Published: 2026-04-09T17:16:31.267
Modified: 2026-04-13T15:02:27.760
Link: CVE-2026-39976
No data.
OpenCVE Enrichment
Updated: 2026-04-10T09:32:05Z
Github GHSA