On 23 October 2026 the GitHub Advisory Database published CVE-2026-114509, a critical authentication bypass in Laravel's built-in TokenGuard. With the standard token-based API guard and a MySQL or MariaDB database, an unauthenticated attacker can log in as another existing user without knowing that user's API token. GitHub rates it Critical with a CVSS v4.0 score of 9.2.
The uncomfortable part is the timeline. The fixed releases, laravel/framework 12.68.0 and 13.29.0, were tagged on 25 August 2026, about two months before the advisory went public. Teams that run composer update regularly are already patched and may not have noticed. Teams whose composer.lock has not moved since the summer are running a known account-takeover bug, and the details are now public.
What happened
Laravel ships several authentication guards. The token guard is the simplest one: a client sends an API token with each request, Laravel looks up the user whose stored token matches, and that user becomes the authenticated user for the request.
The advisory describes a non-string credential value, crafted by the attacker, that is mishandled during that lookup. Under certain database configurations, specifically MySQL and MariaDB, the resulting query matches a user it should not. The attacker never needs the victim's token. Any route behind that guard is then open to them as the matched user (CWE-287, CWE-1287).
A public proof of concept with a Docker lab has been written up by Security Online. There is no confirmed in-the-wild exploitation at the time of writing and the CVE is not on CISA's Known Exploited Vulnerabilities list, but a working PoC tends to change that quickly.
Who is affected
laravel/frameworkbelow 12.68.0, and 13.0.0 up to but not including 13.29.0.- Applications where a guard in
config/auth.phpuses thetokendriver. - Applications backed by MySQL or MariaDB. Other databases are not named in the advisory.
The advisory lists only the 12.x and 13.x lines. It says nothing about Laravel 11.x, and we are not going to guess. If you run 11.x, read the advisory yourself and check the changelog for your installed version rather than assuming you are safe.
How to check in one minute
Run this inside the project directory on the server, or wherever the deployed composer.lock lives:
composer show laravel/framework | grep versions
composer auditIf the version printed is below 12.68.0 or, on 13.x, below 13.29.0, you are exposed. composer audit reads the same advisory database and will flag CVE-2026-114509 along with everything else that applies to your lock file. A second useful check is git log -1 -- composer.lock: if that commit predates 25 August 2026, treat the application as vulnerable until proven otherwise.
Two more advisories in the same batch
The same reporter, KIKOmanasijev, is credited for CVE-2026-114508, published alongside the TokenGuard bug. It is rated Moderate (CVSS 3.1 6.5). A crafted request to a read-only endpoint that includes relationships can trigger a destructive database operation on a related table, with no write permission required. It affects laravel/framework 12.45.0 up to but not including 12.68.0, and 13.0.0 up to but not including 13.27.0. The same upgrade to 12.68.0 or 13.29.0 closes both holes.
Separately, Livewire published GHSA-mhf7-xp6r-6qrc (no CVE yet, CVSS 3.1 6.5). In livewire/livewire 4.3.0 up to but not including 4.4.8, the #[Authorize] attribute can be bypassed in three ways: by reordering integer parameter keys so that authorization checks one record while the action receives another, by the same trick through #[On] event listeners, and because #[Json] methods ran their body before the authorization check, so side effects happened even though the response was still a 403. Livewire 3.x is not affected, and code that calls $this->authorize(...) inside the method is not affected. The fix is 4.4.8, released on 21 October 2026.
What to do now
- Upgrade
laravel/frameworkto 12.68.0 or later, or 13.29.0 or later, and deploy. Do not wait for a maintenance window if you use the token guard on MySQL or MariaDB. - If you cannot upgrade today, consider temporarily disabling the token guard or moving those routes behind a different guard. The advisory lists no configuration-only workaround.
- Upgrade
livewire/livewireto 4.4.8 if you are on 4.3.x or 4.4.x. - Rotate API tokens for sensitive accounts after upgrading. The bypass does not leak tokens, but if you cannot rule out prior abuse, rotation is cheap.
- Review access logs on token-guarded routes for requests from unfamiliar sources since late August, especially ones that succeeded without a plausible token.
- Add
composer auditto your CI pipeline so a fix that ships quietly in a point release gets noticed before the advisory does.
How Scantinel helps
Scantinel runs external scans of your public website: exposed software versions, known-vulnerable components, missing security headers, misconfigurations and files that should not be reachable. Laravel is usually detectable from the outside, but the framework version and the guard configuration are not, and this bug lives entirely in application logic that no external scanner can see. The authoritative check for CVE-2026-114509 is composer show laravel/framework on the server. Run it today, and let Scantinel watch the perimeter you cannot check by hand.
Comments
No comments yet.