CriticalCVE-2026-114509

    framework: Improper Authentication (CVE-2026-114509)

    Published Last modified Sources: BSI

    Share

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. Update Laravel Framework to version 12.68.0.

    Affected
    • Laravel Framework gte 13.0.0, < 13.29.0..*
    • Laravel Framework lt *..12.68.0
    Fixed in
    • Laravel Framework 12.68.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.2

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    9.2

    CVSS v4

    Severity Critical on the scale from 0 to 10.

    Source: BSI

    1.8 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 79.1

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    102.07 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.2 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.2
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    1.8 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    79.1
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 28 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-287, CWE-1287

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: BSI WID Portal

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    laravelframework
    • ≥ 12.45.0, < 12.68.0
    • ≥ 13.0.0, < 13.29.0
    • < 12.68.0
    • —
    • —
    • 12.68.0
    Open SourceLaravel
    • < 12.68.0
    • < 13.29.0
    • 12.68.0
    • 13.29.0
    composerlaravel/framework
    • >= 12.45.0, < 12.68.0
    • < 12.68.0
    • >= 13.0.0, < 13.27.0
    • >= 13.0.0, < 13.29.0
    • 12.68.0
    • 12.68.0
    • 13.27.0
    • 13.29.0
    packagistlaravel/framework
    • 10.50.2
    • 12.45.0
    • 13.0.0
    • 5.0.30
    • 5.2.41
    • v10.0.0
    • v10.0.1
    • v10.0.2
    • v10.0.3
    • v10.1.0
    • v10.10.0
    • v10.10.1
    • v10.1.1
    • v10.11.0
    • v10.1.2
    • v10.12.0
    • v10.1.3
    • v10.13.0
    • v10.13.1
    • v10.13.2
    • v10.13.3
    • v10.13.5
    • v10.1.4
    • v10.14.0
    • v10.14.1
    • v10.1.5
    • v10.15.0
    • v10.16.0
    • v10.16.1
    • v10.17.0
    • v10.17.1
    • v10.18.0
    • v10.19.0
    • v10.2.0
    • v10.20.0
    • v10.21.0
    • v10.21.1
    • v10.22.0
    • v10.23.0
    • —
    • 12.68.0
    • 13.27.0
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    From bundled advisories, not CVE-specific (2)

    Product list of a bundled advisory that does not state which product this CVE affects.

    Products from bundled advisories
    Affected versionsFixed in
    laravellaravel/framework
    • 13.0.0 – < 13.29.0
    • < 12.68.0
    • 13.29.0
    • 12.68.0

    Vendors and products

    Weakness classes (CWE)

    • CWE-287Improper Authentication

      Class

      When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

      Entry at MITRE CWE-287

    • CWE-1287Improper Validation of Specified Type of Input

      Base

      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.

      Entry at MITRE CWE-1287

    References & sources

    • github.comlaravel/framework/security/advisories/GHSA-f9x3-7vq9-cph6x_refsource_CONFIRM, pwn-watch, web
    • github.comlaravel/framework/commit/8dbb08bccac1be095dba4a9d259a419620f1e8…x_refsource_MISC, web
    • github.comlaravel/framework/commit/9b21ce0a9bb2b2599978bc0b0df4abea952ad3…x_refsource_MISC, web
    • github.comlaravel/framework/releases/tag/v12.68.0x_refsource_MISC, pwn-watch, web
    • github.comlaravel/framework/releases/tag/v13.29.0x_refsource_MISC, pwn-watch, web
    • pwn.watchpwn.watch: Laravel TokenGuard authentication bypass through non-string API credentials (CVE-2026-114509)pwn-watch
    • GitHub Security AdvisoriesGHSA-f9x3-7vq9-cph6pwn-watch
    • NVD (NIST)CVE-2026-114509pwn-watch, advisory
    • github.comlaravel/frameworkpackage
    • github.comlaravel/framework/security/advisories/GHSA-5wcm-3v2w-8362x_refsource_CONFIRM, web
    • github.comlaravel/framework/pull/61322x_refsource_MISC, web
    • github.comlaravel/framework/pull/61323x_refsource_MISC, web
    • github.comlaravel/framework/commit/50a7970efe9f9990b6ec4f1e949de2abaaf426…x_refsource_MISC, web
    • github.comlaravel/framework/commit/b89f2944995d555bfda76dced1ef6c6b04ef17…x_refsource_MISC, web
    • github.comlaravel/framework/releases/tag/v13.27.0x_refsource_MISC, web
    • NVD (NIST)vuln/detail/CVE-2026-114508advisory

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-114509","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-28T18:32:04.286628Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      CVSS V4.0: AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

      Weakness type: CWE-287, CWE-1287

      Description added or changed

      Show 10 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      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
      Weakness type (CWE)added
      —
      CWE-287
      Weakness type (CWE)added
      —
      CWE-1287
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/114xxx/CVE-2026-114509.json">CVE-2026-114509</a>
      Referenceadded
      —
      https://github.com/laravel/framework/commit/8dbb08bccac1be095dba4a9d259a419620f1e8a5
      Referenceadded
      —
      https://github.com/laravel/framework/commit/9b21ce0a9bb2b2599978bc0b0df4abea952ad31c
      Referenceadded
      —
      https://github.com/laravel/framework/releases/tag/v12.68.0
      Referenceadded
      —
      https://github.com/laravel/framework/releases/tag/v13.29.0
      Referenceadded
      —
      https://github.com/laravel/framework/security/advisories/GHSA-f9x3-7vq9-cph6

      Source identifier: security-advisories@github.com

    Linked CVEs

    Linked CVEs
    CriticalCVE-2026-114509Laravel TokenGuard authentication bypass through non-string API credentials——
    MediumCVE-2026-114508Laravel relationship inclusion can trigger unauthorized data destruction6.5—
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-114509
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-114509"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-114509.svg?lang=en" alt="CVE-2026-114509 – NEOSEC Intel" height="20"></a>