Black Friday60% off BLACKFRIDAY2026
Platform
PlansPartners
Resources
ToolsBlogDocs
Sign Up →
CVE

CVE-2026-114509

9.2
CVSScritical
Exploitable remotely over the internet · no authentication required.
Description

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. Under affected MySQL or MariaDB configurations, the authentication lookup can match an unintended existing user, allowing an unauthenticated attacker to bypass authentication and take over an account on routes protected by TokenGuard. This issue is fixed in versions 12.68.0 and 13.29.0.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
framework
Updated Nov 17, 2026View on NVD →
S4E scanner

Laravel TokenGuard - Authentication Bypass

Laravel's TokenGuard (driver => token, hash => false) does not validate the credential type before the database lookup. Sending a JSON body with api_token as an array of integers ({"api_token":[0]}) produces a whereIn('api_token', [0]) query; under MySQL/MariaDB implicit casting, every varchar token not starting with a digit evaluates to 0, so the first user row is returned to an unauthenticated attacker. References: https://github.com/laravel/framework/security/advisories/GHSA-f9x3-7vq9-cph6 https://github.com/ArioVeisa/cve-2026-114509-laravel-tokenguard https://nvd.nist.gov/vuln/detail/CVE-2026-114509 Remediation: Update to versions 12.68.0 or 13.29.0 or later.

url

CVE history: framework

Predict next CVE date with AI

Monitor this CVE on your assets

S4E maps published CVEs to scanners and forecasts the next disclosure window for your stack.

Create a free account →