Laravel TokenGuard authentication bypass through non-string API credentials
Laravel's built-in TokenGuard, **when configured with a standard token-based API guard**, may be bypassed to authenticate as an arbitrary existing user without knowledge of their valid API token. **Under certain database configurations (MySQL/MariaDB)** an attacker can submit a specially crafted, non-string credential value that is mishandled during the authentication lookup, causing the underlying query to match an unintended user record rather than failing authentication as expected. ### Impact An unauthenticated attacker may authenticate as another user without possessing that user's API token, leading to authentication bypass and account takeover on any route protected by the affected guard.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-114509US | — | Exploit | ||
Laravel is a web application framework. Prior to 12.68.0 and 13.29.0, TokenGuard configured as a standard token-based API guard does not reject a crafted non-string credential. Und… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/laravel/frameworkPACKAGE
- https://github.com/laravel/framework/commit/8dbb08bccac1be095dba4a9d259a419620f1e8a5WEB
- https://github.com/laravel/framework/commit/9b21ce0a9bb2b2599978bc0b0df4abea952ad31cWEB
- https://github.com/laravel/framework/releases/tag/v12.68.0WEB
- https://github.com/laravel/framework/releases/tag/v13.29.0WEB
- https://github.com/laravel/framework/security/advisories/GHSA-f9x3-7vq9-cph6WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-114509ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan