Laravel Framework Flaw CVE-2026-114509: Update Now
Published October 31, 2026 · Last updated October 31, 2026
The short version: CVE-2026-114509 is a critical-severity security flaw in Laravel Framework. The National Vulnerability Database (NVD) published it on October 21, 2026, and the score it lists is 9.2 out of 10. When FraudMeNot checked on October 31, 2026, CISA had not added CVE-2026-114509 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
What the official record says about CVE-2026-114509
The record was filed by github.com. In its own words: "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."
Why Laravel Framework admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on github.com rated CVE-2026-114509 9.2 (Critical) under CVSS 4.0. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Laravel Framework running is high. Scoring string: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X.
Affected Laravel Framework releases
According to the record, these releases are vulnerable:
- version < 12.68.0
- version >= 13.0.0, < 13.29.0
The type of bug behind CVE-2026-114509
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-287, Improper Authentication. MITRE describes this class of bug as follows: "When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct."
- CWE-1287, Improper Validation of Specified Type of Input. MITRE describes this class of bug as follows: "The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type."
Vendor remediation for CVE-2026-114509
The vendor advisory remediation for operators of Laravel Framework, quoted for this page, is: "Update laravel/framework to 13.29.0 or later on the 13.x line, or 12.68.0 or later on the 12.x line, per the GitHub security advisory GHSA-f9x3-7vq9-cph6, then run composer update, commit the new composer.lock, and redeploy every environment. Priority goes to Laravel apps whose API routes use the standard token-based TokenGuard and whose database is MySQL or MariaDB, since the record says the unintended user match happens under affected configurations of those two databases. Apps on older, unsupported Laravel major versions should plan an upgrade to a maintained line that receives this fix."
What to do about it
- Update now: Update laravel/framework to 13.29.0 or later on the 13.x line, or 12.68.0 or later on the 12.x line, per the GitHub security advisory GHSA-f9x3-7vq9-cph6, then run composer update, commit the new composer.lock, and redeploy every environment. Priority goes to Laravel apps whose API routes use the standard token-based TokenGuard and whose database is MySQL or MariaDB, since the record says the unintended user match happens under affected configurations of those two databases. Apps on older, unsupported Laravel major versions should plan an upgrade to a maintained line that receives this fix.
- Who should act: IT teams, managed service providers, and developers who run or ship Laravel Framework. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from Laravel (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from October 21, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-114509. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-114509 record details from CISA and NVD
- Attack complexity for CVE-2026-114509: low
- CVE-2026-114509 attack requirements: present
- Impact on connected systems: secrecy none, integrity none, availability none.
- Who mapped the weakness type: the address listed on github.com (Secondary)
- References in the NVD record: 5.
- CISA SSVC decision points for CVE-2026-114509 (from NVD): exploitation=none; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).
Dates to know
- October 21, 2026: NVD publishes CVE-2026-114509.
- October 31, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-114509 is not listed.
- October 28, 2026: most recent NVD update (record status: Awaiting Analysis).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
- github.com/laravel/framework/commit/8dbb08bccac1be095dba4a9d259a419620f1e8a5
- github.com/laravel/framework/commit/9b21ce0a9bb2b2599978bc0b0df4abea952ad31c
- github.com/laravel/framework/releases/tag/v12.68.0
- github.com/laravel/framework/releases/tag/v13.29.0
- github.com/laravel/framework/security/advisories/GHSA-f9x3-7vq9-cph6
Sources
- NVD: CVE-2026-114509
- CVE.org: CVE-2026-114509
- Laravel advisory
- Laravel advisory
- Laravel advisory
- MITRE CWE-287
- MITRE CWE-1287
General education only, not security advice. Facts checked against the sources above on the date shown.