laravel/framework security advisory

CVE-2026-114509: Laravel TokenGuard authentication bypass through non-string API credentials

CVE-2026-114509 is a critical-severity authentication bypass vulnerability in the PHP package laravel/framework (CVSS 9.2), published 21 October 2026. It is fixed in 12.68.0 and 13.29.0, one per release line; earlier versions on each line are affected. It can be exploited without an account.

critical 9.2 published 2026-10-21 · updated 2026-10-28

Affected versions: < 12.68.0
>= 13.0.0, < 13.29.0
Fixed in: 12.68.0, 13.29.0
Newest release: 13.40.0
Severity: Critical · CVSS 9.2
Type: Authentication bypass
CWE-287, CWE-1287
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your laravel/framework version affected?

Run composer show laravel/framework in your project, then enter the version. We check it against this and every other known laravel/framework advisory.

Who can exploit CVE-2026-114509

Access: No account. Anyone who can send a request to an app that uses the affected code.
Conditions: It only works under specific conditions the attacker does not fully control (CVSS rates the attack as high complexity).

CVSS vector (scored by GitHub): 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

Your app is only exposed if it uses the affected part of laravel/framework. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-114509 in laravel/framework

Find the installed version: composer show laravel/framework. If you never required it yourself, composer why laravel/framework shows which package pulls it in.
Update it: composer update laravel/framework --with-all-dependencies. You need the fixed version for your release line (12.68.0 and 13.29.0).
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "laravel/framework": "^13.29.0" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-114509.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for authentication bypass issues while the upgrade waits. None of it replaces the fix.

Remove accounts you do not need and review what each role can do.
Put the admin area behind a VPN, IP allow-list or extra login until you upgrade.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-114509 advisory

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.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-114509. Advisory title: “Laravel TokenGuard authentication bypass through non-string API credentials”.

References

GitHub advisory GHSA-f9x3-7vq9-cph6 github.com
Fix commit 8dbb08b github.com
Fix commit 9b21ce0 github.com
Release v12.68.0 github.com
Release v13.29.0 github.com

Other laravel/framework advisories

medium CVE-2026-114508: Laravel relationship inclusion can trigger unauthorized data destruction 2026-10-23
low CVE-2026-102279: Laravel: XSS in Debug Page Information 2026-09-29
medium Laravel Framework: Temporary Signed URL Path Confusion 2026-06-17
high Laravel Framework: CRLF injection in default email rule 2026-06-17
CVE-2026-48019: Laravel CRLF injection in default email rule 2026-05-19
medium CVE-2025-27515: Laravel has a File Validation Bypass 2025-03-05

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.