Live › vulnerability › CVE-2026-114509
Go to dashboardLaravel's built-in TokenGuard can be tricked into authenticating as an existing user when an attacker sends a crafted non-string API token value. On MySQL or MariaDB the authentication query matches an unintended user record, so an attacker gets that user's account without their token.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:51 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| laravel/framework | composer | >= 13.0.0, < 13.29.0 | 13.29.0 |
| laravel/framework | composer | < 12.68.0 | 12.68.0 |
Run: composer show laravel/framework | grep versions
Check config/auth.php for guards with driver => token
Confirm the database driver is MySQL or MariaDB
13.29.0 or later on the 13.x line, or 12.68.0 or later on the 12.x lineEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-114509")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.