Laravel TokenGuard Auth Bypass (CVE-2026-114509, CVSS 9.2): A Non-String Token Can Log an Attacker In as Anyone

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Laravel TokenGuard Auth Bypass (CVE-2026-114509, CVSS 9.2): A Non-String Token Can Log an Attacker In as Anyone

Authentication guards fail in two ways: loudly, and in the direction nobody tests. CVE-2026-114509 is the second kind. Laravel's built-in TokenGuard — the simple token driver many APIs still use — can be bypassed with a specially crafted non-string credential: under MySQL or MariaDB, the malformed value is mishandled during the authentication lookup, the query matches an unintended user record, and an unauthenticated attacker is authenticated as an existing user, without that user's API token.

What Happened

The vendor advisory (GHSA-f9x3-7vq9-cph6) was published October 19, 2026, and the CVE record followed on October 21.

Am I Affected?

There is an honest limitation to state up front: no outside scanner — including ours — can see your Laravel version or your guard configuration. Framework versions are not announced to the internet, and they shouldn't be. This check lives where the code lives:

  1. composer show laravel/framework — or read composer.lock. Below 12.68.0 / 13.29.0 means the vulnerable code is present.
  2. config/auth.php — is any guard using 'driver' => 'token'?
  3. Is that guard's user provider backed by MySQL or MariaDB?

All three true means the bypass applies to every route behind that guard. Patch, then treat tokens and sessions issued under the old code with suspicion proportional to how public those routes were.

What To Do Now

  1. Update to laravel/framework 12.68.0 / 13.29.0 or later. The advisory lists no workaround — the update is the fix.
  2. Audit authentication logs for the token guard's routes: successful authentications that don't correspond to a plausible token are the fingerprint of this bug being used.
  3. Consider migrating API authentication to Sanctum or Passport if you're still on the built-in token guard — not because they were named here (they weren't), but because the simple guard gets the least ongoing scrutiny.

The Pattern Worth Remembering

The input that broke this was not a clever string — it was a value of the wrong type. Type-juggling at trust boundaries is one of the oldest bug classes in PHP applications, and it survives because test suites send well-formed credentials. Whatever guard you run, the adversarial cases are the malformed ones: arrays where strings belong, nulls where values belong, numbers where tokens belong. If your auth tests only try wrong credentials and never weird ones, this CVE is your reminder to add the weird ones.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report