cve.bz

CVE-2026-114509 laravel framework: Improper Authentication

9.2 criticalEPSS 1.8%Fix available

Critical (9.2) in laravel framework. EPSS 1.8% estimated probability of exploitation activity in the next 30 days. Fixed in laravel/framework 10.50.4, 11.56.1, 12.68.0.

On this page
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.

Severity

CVSS 4.0

9.2 critical
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
EPSS
1.8% (unchanged from 1.8% a week ago) estimated probability of exploitation activity in the next 30 days; 79th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-287 Improper Authentication
CWE-1287 Improper Validation of Specified Type of Input
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-114509 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114509?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114509?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114509 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
laravel framework< 12.68.0
laravel framework>= 13.0.0, < 13.29.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f9x3-7vq9-cph6Packagistlaravel/framework>=13.0.0 <13.27.013.27.0
GHSA-f9x3-7vq9-cph6Packagistlaravel/framework>=12.0.0 <12.68.012.68.0
GHSA-f9x3-7vq9-cph6Packagistlaravel/framework>=11.0.0 <11.56.111.56.1
GHSA-f9x3-7vq9-cph6Packagistlaravel/framework<10.50.410.50.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13php-laravel-frameworkno fix listedDEBIAN-CVE-2026-114509
Debian14php-laravel-framework13.31.0+dfsg-1DEBIAN-CVE-2026-114509

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • hakaioffsec/CVE-2026-114509-PoC Harbor Check: matches CVE 13 stars, Python, created
    A poc for https://github.com/laravel/framework/security/advisories/GHSA-f9x3-7vq9-cph6
  • Nxploited/CVE-2026-114509 Harbor Check: matches CVE 2 stars, Python, created
    Laravel TokenGuard authentication bypass through non-string API credentials
  • dimasma0305/CVE-2026-114509 Harbor Check: matches CVE 1 star, Python, created
    Reproducible local Laravel lab and self-checking PoC for CVE-2026-114509
  • tajulasri/-CVE-2026-114509-POC Harbor Check: matches CVE 1 star, Blade, created
    CVE-2026-114509-POC [Educational Purpose Only]
  • ArioVeisa/cve-2026-114509-laravel-tokenguard Harbor Check: matches CVE 0 stars, PHP, created
    CVE-2026-114509 — Laravel TokenGuard authentication bypass (CVSS 9.2): PoC, root-cause analysis, Docker lab, and reproduction guide

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON