Skip to content

Get notified

Get an email when a new major security incident drops. No spam, unsubscribe any time.

Only used for pwn.watch incident emails. Protected by Cloudflare Turnstile.

Become a sponsor

One slot: pwn.watch, gifs.so, flavors.design, kitze.io, every kitze repo, and an X shout-out.

Secure checkout on Polar. Right after paying you set up your ad on kitze.io.

LivePatchedPatch now

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

Laravel framework (laravel/framework) TokenGuard

Laravel's built-in TokenGuard, when configured as a standard token-based API guard, can be bypassed to log in as an arbitrary existing user without their API token. On some database configurations (MySQL/MariaDB), a crafted non-string credential is mishandled during the lookup so the query matches an unintended user instead of failing. An unauthenticated attacker can take over accounts on any route protected by that guard. Upgrade laravel/framework to 12.68.0 or 13.29.0. GitHub rates it critical (CVSS 4.0 score 9.2).

Why this severity: CVSS 4.0 9.2 per GitHub; only apps using the built-in token API guard on MySQL/MariaDB-style configurations

Started
Oct 23, 2026

Follow this incident

Discuss on X ↗

Affected

  • laravel/framework < 12.68.0
  • laravel/framework >= 13.0.0, < 13.29.0

Fixed in

  • laravel/framework 12.68.0
  • laravel/framework 13.29.0

Timeline1

  1. Laravel publishes GHSA-f9x3-7vq9-cph6 (CVE-2026-114509); fixes ship in laravel/framework 12.68.0 and 13.29.0.

Advisories5

Get an email when a new major security incident drops. No spam, unsubscribe any time.