Advisory record · GHSA-f9x3-7vq9-cph6

Laravel TokenGuard authentication bypass through non-string API credentials

CVSS 9.2 CriticalCriticalEPSS 0.018 · 79th percentile

Critical, because:

  • CVSS score 9.2: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 23 Oct 2026, 21:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
laravel/frameworkPackagist>=13.0.0, <13.29.0 || <12.68.013.29.0, 12.68.0
Identifiers
GHSA-f9x3-7vq9-cph6 · CVE-2026-114509 · PKSA-b41t-wbzk-9q51
Weakness (CWE)
CWE-287 · CWE-1287
Published
23 Oct 2026
Updated
23 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Laravel framework versions before 12.68.0, and from 13.0.0 before 13.29.0, have an authentication bypass in the built-in TokenGuard when it is configured with a standard token-based API guard. On MySQL or MariaDB databases, an unauthenticated attacker who submits a specially crafted non-string credential can match another existing user's record and log in as that user without their API token, gaining access to routes protected by that guard. Upgrade laravel/framework to 12.68.0, 13.29.0, or a later release.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.2 Critical 4.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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.018, the 79th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:53 UTC First seen by agentprime
  2. 31 Oct 2026, 13:53 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.