# Laravel TokenGuard authentication bypass through non-string API credentials Advisory record · `GHSA-f9x3-7vq9-cph6` - **Identifiers:** `GHSA-f9x3-7vq9-cph6` · `CVE-2026-114509` · `PKSA-b41t-wbzk-9q51` - **State:** Confirmed - **Severity:** CVSS 9.2 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-1287](https://cwe.mitre.org/data/definitions/1287.html) - **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-1287](https://agentprime.io/advisories/tag/cwe-1287.md) - **Published:** 23 Oct 2026 - **Updated:** 23 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 23 Oct 2026, 21:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.2: 9.0 or more. How we decide what’s critical: ## Affected packages - `laravel/framework` (Packagist): affected `>=13.0.0, <13.29.0 || <12.68.0`; fixed in `13.29.0`, `12.68.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Laravel framework versions before 12.68.0, and from 13.0.0 before 13.29.0, have an authentication bypass in the built-in TokenGuard when it is configured with a standard token-based API guard. On MySQL or MariaDB databases, an unauthenticated attacker who submits a specially crafted non-string credential can match another existing user's record and log in as that user without their API token, gaining access to routes protected by that guard. Upgrade laravel/framework to 12.68.0, 13.29.0, or a later release. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.2 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.018, the 79th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 13:53 UTC: First seen by agentprime - 31 Oct 2026, 13:53 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f9x3-7vq9-cph6) ## Sources - [GitHub Advisory Database: GHSA-f9x3-7vq9-cph6](https://github.com/advisories/GHSA-f9x3-7vq9-cph6) - [OSV: GHSA-f9x3-7vq9-cph6](https://osv.dev/vulnerability/GHSA-f9x3-7vq9-cph6) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .