Authentication Bypass in Laravel Passport (CVE-2026-39976)
Summary
Authentication bypass in Laravel Passport (CVE-2026-39976). Confidential information can be exposed externally. Mitigation: upgrade to 13.7.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-39976 has been found in Laravel Passport.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade Laravel Passport to 13.7.1 or later.
If unsure, ask your IT team or search "Laravel Passport CVE-2026-39976" on the vendor's site.
CVE-2026-39976 (Laravel Passport) — CWE-287 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 13.7.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in Laravel Passport.
Check the vendor advisory for the affected versions of Laravel Passport.
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.
Update to 13.7.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Passport' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Passport' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Passportを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Laravel Passport to 13.7.1ステージング環境で 13.7.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- report github.com
- report github.com