CVE-2026-114509
🟠 Mediumlaravel/framework — TokenGuard used as a token-based API guard (MySQL / MariaDB back ends) · < 12.68.0 ; ≥ 13.0.0 and < 13.29.0
CVSS (Koffei note)
9.2CVSS (v4.0, CVE List)
9.2EPSS (2026-11-18)
1.840%79.41th percentile
Exploitation
No — no exploitation found ; the record carries no CISA ADP block, so there is no SSVC value ; not in KEV ; no public PoC found
Timeline
- 21/10/2026CVE record published (CVE List)
- 23/10/2026Laravel TokenGuard authentication bypass
Risk
9.2 Critical (v4.0, GitHub CNA) — AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H, EPSS 0.403% (CWE-287 / CWE-1287 :
TokenGuard does not reject a non-string API credential, so on MySQL/MariaDB the type-juggled authentication lookup matches an unintended existing user — pre-authentication account takeover on any TokenGuard-protected route)Fix
Yes — 12.68.0 / 13.29.0 (GHSA-f9x3-7vq9-cph6)
Official 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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CWE-1287,CWE-287