Is CVE-2026-114509 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114509 being exploited in the wild.

How severe is CVE-2026-114509?

Critical severity, with a CVSS score of 4, published 21 October 2026.

Which products and versions are affected?

Laravel prior to 12.68.0, 13.29.0; laravel/framework (Packagist) >= 13.0.0, < 13.29.0, ECOSYSTEM:introduced=13.0.0,fixed=13.29.0.

Is there a fix for CVE-2026-114509?

Yes. laravel/framework (Packagist): upgrade to 13.29.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114509 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-114509?

Check whether you run Laravel or laravel/framework (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114509: Laravel TokenGuard authentication bypass via non-string credential

Q: Is there a fix for CVE-2026-114509?

Yes. laravel/framework (Packagist): upgrade to 13.29.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-114509 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-114509?

Check whether you run Laravel or laravel/framework (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114509 · Severity: critical · CVSS 4 · Published 2026-10-21

Laravel is a popular web application framework used to build dynamic websites and APIs. TokenGuard is a built-in authentication component that validates API requests using token credentials. An attacker can bypass authentication on affected applications by sending a specially crafted non-string token, potentially allowing them to take over user accounts on protected routes—especially when the database uses MySQL or MariaDB with certain configurations that treat different data types as equivalent during lookups.

Technologies: Laravel, laravel/framework (Packagist). Vendors: Laravel, Packagist.

Quick answers

Is CVE-2026-114509 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114509 being exploited in the wild.
How severe is CVE-2026-114509?: Critical severity, with a CVSS score of 4, published 21 October 2026.
Which products and versions are affected?: Laravel prior to 12.68.0, 13.29.0; laravel/framework (Packagist) >= 13.0.0, < 13.29.0, ECOSYSTEM:introduced=13.0.0,fixed=13.29.0.
Is there a fix for CVE-2026-114509?: Yes. laravel/framework (Packagist): upgrade to 13.29.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114509 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-114509?: Check whether you run Laravel or laravel/framework (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

laravel/framework (Packagist): upgrade to 13.29.0 or later
```
composer require laravel/framework:^13.29.0
```

Technical details

TokenGuard's authentication handler fails to enforce strict type checking on credentials, allowing non-string tokens to reach the database lookup layer. Under certain MySQL/MariaDB configurations where type juggling or loose comparison occurs, a crafted credential (e.g., a numeric value) can match an unintended existing user's token, resulting in authentication bypass. The vulnerability affects Laravel versions prior to 12.68.0 and 13.29.0; fixes enforce strict string validation on token retrieval.

Affected products

Laravel Laravel prior to 12.68.0, 13.29.0

Identifiers

CVE-2026-114509
GHSA-f9x3-7vq9-cph6

Timeline

2026-10-21: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.