Back to Blog
Legacy Modernization

Laravel security vulnerability CVE-2026-114509: what to check this week

5 min read
CTOs
IT managers
Laravel teams

Laravel has published a critical security advisory, CVE-2026-114509, rated 9.2 out of 10 (CVSS v4). Security researchers saw exploit attempts on 27 Oct. If your business runs on Laravel, here is what the flaw is, how to check whether you're exposed, and what to do if you're on an older version.

In short: CVE-2026-114509 is a critical Laravel flaw where the built-in TokenGuard can be tricked by a non-string API token on MySQL or MariaDB, letting an attacker log in as an existing user. It is fixed in Laravel 12.68.0 and 13.29.0. Older versions, including Laravel 11 and earlier, get no fix, so they need an upgrade.

What the flaw is, in plain English

Laravel's built-in TokenGuard checks the API token sent with a request and finds the matching user. On some database setups, named in the advisory as MySQL and MariaDB, a token sent as something other than text (for example, a list) is mishandled during that lookup. The result can be that an attacker is logged in as an existing user without that user's token.

The advisory describes the impact as authentication bypass and account takeover on any route protected by the affected guard.

Who is exposed

You are likely exposed if all of these are true:

  • Your app runs a Laravel version below 12.68.0, or a 13.x version below 13.29.0
  • Your API uses Laravel's built-in TokenGuard (a guard with the token driver)
  • The routes behind that guard use MySQL or MariaDB
  • Running Laravel, or having an /api/user route, doesn't on its own mean you're exposed. If your API uses a different authentication package, the advisory doesn't cover it, so ask your developer which guard your API uses rather than assume either way.

    What's been seen so far

    Security researchers saw exploit attempts against a test Laravel app on 27 Oct, using the payload from a public proof of concept. That attempt failed, but the researchers expect successful attempts against affected setups. Treat this as a job for this week, not next quarter.

    Check your exposure: a checklist

  • Find your Laravel version: run composer show laravel/framework.
  • On Laravel 12? Update to 12.68.0 or later. On Laravel 13? Update to 13.29.0 or later.
  • On Laravel 11 or older? There is no patched release. Plan an upgrade (see below).
  • Open config/auth.php and look for any guard using the token driver. Note which API routes it protects.
  • Check which database those routes use. MySQL and MariaDB are the configurations named in the advisory.
  • Search your request logs for api_token sent as an array, for example {"api_token": [0]}, including on GET requests.
  • If you find matches, check whether those requests returned user data or were followed by unusual account activity.
  • Is there a quick workaround?

    Updating Laravel is the fix. MySQL strict mode is not a substitute for it. A firewall rule that blocks array-valued api_token may help while you update, but don't rely on it.

    The bigger issue: old Laravel versions get no fix

    There is no fixed 11.x, 10.x, 9.x or 8.x release. Laravel's own support policy explains why: security fixes for Laravel 10 ended on 4 Feb 2025 and for Laravel 11 on 12 Mar 2026. Laravel 12 gets security fixes until 24 Feb 2027, and Laravel 13 until 17 Mar 2028.

    So if your app is on Laravel 11 or older, the fix is an upgrade, not a patch. If you're upgrading anyway, moving to 13 buys you more time than 12.

    It's the same lesson as the PHP2Shell vulnerability: versions that no longer get security fixes leave you waiting for a patch that never comes. The usual options are:

  • Upgrade in place, if the codebase is in good shape and the version gap is small
  • Step through each major version, with tests at every step, if the gap is bigger
  • Rebuild parts of the app, where the code is too tangled to upgrade safely
  • Whichever route fits, the safe way is the same: tests first, small releases, a phased rollout and a rollback plan. If you're weighing these options, our guides on when to replace a legacy system and choosing a partner for legacy modernisation can help.

    FAQ

    Is every Laravel app vulnerable?

    No. The advisory covers the built-in TokenGuard with MySQL or MariaDB. Exposure depends on your guard, database and data, so check rather than assume.

    I'm on Laravel 8, 9, 10 or 11. Is there a patch?

    No. Those versions no longer get security fixes, so the fix is upgrading to 12.68.0 or later, or 13.29.0 or later.

    Should I go to Laravel 12 or 13?

    Laravel 12 security fixes end on 24 Feb 2027 and Laravel 13 on 17 Mar 2028. If you're upgrading anyway, 13 gives you longer.

    Is it being exploited?

    Researchers saw exploit attempts on 27 Oct. The attempt they saw failed, but they expect successful ones against affected setups.

    Can a firewall rule or database setting fix it?

    Updating Laravel is the fix. A rule blocking array-valued api_token may help in the meantime, but don't rely on it.

    Need a hand?

    On an older Laravel version? Book a free consult and we'll check what you're running and map the upgrade path. We can do the upgrade as your tech team, or join your developers as a senior team. See our Legacy Modernisation services or message us on WhatsApp +971 585692165.

    Sources: Laravel security advisory GHSA-f9x3-7vq9-cph6, GitHub advisory database entry, Laravel releases v12.68.0 and v13.29.0, Laravel support policy. Checked on 29 Oct 2026.