Threat Pulse 62High
Laravel TokenGuard auth bypass (CVE-2026-114509, CVSS 9.2): log in as any user
Severity 4PatchedconfirmedWeb servers and gateways

Laravel's token API guard did not check that a submitted token was a string, so on MySQL or MariaDB a crafted non-string value could match another user's row and log the attacker in without a token. Apps using 'driver' => 'token' are affected; Sanctum and Passport are not. Fixed in laravel/framework 12.68.0 and 13.29.0.

What to do: Upgrade to 12.68.0 or 13.29.0; reproduction repo is public.

· 16 days ago · Laravel apps using the token guard on MySQL/MariaDB · Laravel News
SourcesLaravel NewsGitLab Advisory DatabaseCyber Kendra
Why this score

Hundreds of thousands of Laravel apps but only those using the token guard on MySQL (impact 2), public reproduction available (exploitability 1), general sector (criticality 0), plus a 9.2 CVSS.

Back to the board

Updated Nov 5, 01:47 UTC. Refreshes on its own.

Add a threat

Paste a link to an advisory, an article or an X post. A person reads every submission before it shows; nothing posts on its own.

Share

The picture people see when the link is posted
Post on XSave picture

This picture is what X, iMessage, Slack and Facebook show under the link. It is drawn fresh from the live board: the board and chart pictures update every 10 minutes, an event picture follows that event.