{"answers":{"affected":"2 open source packages ship an affected version, including laravel/passport. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-39976 in the wild and no public exploit code.","fix":"Upgrade laravel/passport to 13.7.1 or later.","what":"CVE-2026-39976 is a high-severity authentication bypass vulnerability in laravel passport, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-39976 and fix it if it is affected.\n\nWhat it is: CVE-2026-39976 is a high-severity authentication bypass vulnerability in laravel passport, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-39976 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- laravel/passport (Packagist): affected from 13.0.0; fixed in 13.7.1\n- laravel/passport (Packagist): affected from 13.0.0; fixed in 13.7.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-39976/ (Markdown: https://insights.sbomify.com/CVE-2026-39976/index.md)","id":"CVE-2026-39976","markdown":"https://insights.sbomify.com/CVE-2026-39976/index.md","name":"CVE-2026-39976","record":{"aliases":["GHSA-349c-2h2f-mxf6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel Passport","requires_auth":"low_privilege","summary":"Attackers can use machine-to-machine tokens to authenticate as unrelated real users due to improper validation of client credentials.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"passport","vendor":"laravel"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Laravel Passport's TokenGuard Authenticates Unrelated User for Client Credentials Tokens","id":"CVE-2026-39976","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"flatpak-builder has a path traversal leading to arbitrary file read on host when installing licence files","id":"CVE-2026-39977"},"packages":[{"ecosystem":"Packagist","fixed":["13.7.1"],"introduced":["13.0.0"],"last_affected":[],"package":"laravel/passport","purl":null,"source":"GHSA-349c-2h2f-mxf6"},{"ecosystem":"Packagist","fixed":["13.7.1"],"introduced":["13.0.0"],"last_affected":[],"package":"laravel/passport","purl":"pkg:composer/laravel/passport","source":"GHSA-349c-2h2f-mxf6"}],"prev":{"headline":"Combodo iTop: Remote code execution using external auth variable value","id":"CVE-2026-39975"},"products":["passport"],"published":"2026-04-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-09","vendors":["laravel"]},"summary":"Attackers can use machine-to-machine tokens to authenticate as unrelated real users due to improper validation of client credentials.","url":"https://insights.sbomify.com/CVE-2026-39976/"}