CVE-2026-39976: CWE-287: Improper Authentication in laravel passport
A vulnerability in Laravel Passport versions 13. 0. 0 through before 13. 7. 1 allows an authentication bypass for client_credentials tokens. The issue arises because the JWT 'sub' claim is set to the client identifier, which the token guard uses to retrieve a user without validating that the identifier corresponds to an actual user. This can cause machine-to-machine tokens to authenticate as unrelated real users. The vulnerability is fixed in version 13. 7. 1.
AI Analysis
Technical Summary
Laravel Passport, an OAuth2 server implementation for Laravel, versions 13.0.0 up to but not including 13.7.1, contains an authentication bypass vulnerability (CWE-287). The underlying league/oauth2-server library sets the JWT 'sub' claim to the client identifier for client_credentials tokens, which lack a user context. Laravel Passport's token guard uses this 'sub' claim to retrieve a user by ID without verifying that the ID corresponds to a real user. Consequently, a machine-to-machine token may inadvertently authenticate as an unrelated legitimate user. This flaw was addressed and fixed in version 13.7.1.
Potential Impact
An attacker with a valid client_credentials token can bypass intended authentication controls and impersonate an unrelated real user. This leads to unauthorized access with potentially high confidentiality impact, as the attacker may gain access to user-specific resources or data. The integrity impact is lower but still present due to limited modification capabilities, and availability is not affected. The CVSS score is 7.1 (High).
Mitigation Recommendations
Upgrade Laravel Passport to version 13.7.1 or later, where this authentication bypass vulnerability is fixed. There is no indication of alternative mitigations or temporary workarounds. Patch status is not explicitly stated but the fix is available in the specified version.
CVE-2026-39976: CWE-287: Improper Authentication in laravel passport
Description
A vulnerability in Laravel Passport versions 13. 0. 0 through before 13. 7. 1 allows an authentication bypass for client_credentials tokens. The issue arises because the JWT 'sub' claim is set to the client identifier, which the token guard uses to retrieve a user without validating that the identifier corresponds to an actual user. This can cause machine-to-machine tokens to authenticate as unrelated real users. The vulnerability is fixed in version 13. 7. 1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Laravel Passport, an OAuth2 server implementation for Laravel, versions 13.0.0 up to but not including 13.7.1, contains an authentication bypass vulnerability (CWE-287). The underlying league/oauth2-server library sets the JWT 'sub' claim to the client identifier for client_credentials tokens, which lack a user context. Laravel Passport's token guard uses this 'sub' claim to retrieve a user by ID without verifying that the ID corresponds to a real user. Consequently, a machine-to-machine token may inadvertently authenticate as an unrelated legitimate user. This flaw was addressed and fixed in version 13.7.1.
Potential Impact
An attacker with a valid client_credentials token can bypass intended authentication controls and impersonate an unrelated real user. This leads to unauthorized access with potentially high confidentiality impact, as the attacker may gain access to user-specific resources or data. The integrity impact is lower but still present due to limited modification capabilities, and availability is not affected. The CVSS score is 7.1 (High).
Mitigation Recommendations
Upgrade Laravel Passport to version 13.7.1 or later, where this authentication bypass vulnerability is fixed. There is no indication of alternative mitigations or temporary workarounds. Patch status is not explicitly stated but the fix is available in the specified version.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-08T00:01:47.628Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d7dc7c1cc7ad14daf451de
Added to database: 4/9/2026, 5:06:04 PM
Last enriched: 4/9/2026, 5:20:45 PM
Last updated: 4/9/2026, 7:21:07 PM
Views: 24
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.