Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/nguemoue/project2026_20261030_tokengate
Defensive ToolsStatic AnalysisVulnerability ScannersVulnerability AnalysisCode AnalysisConfiguration AuditingWeb SecurityDevSecOpsAuthentication
Share
GitHubnguemoue/project2026_20261030_tokengate

project2026_20261030_tokengate

Un fichier PHP, zéro dépendance : dit si laravel/framework est encore sous le correctif TokenGuard (CVE-2026-114509). Aucun exploit, aucun réseau.

View Repository
22 days agoNot yet reviewed

tokengate

One PHP file. No Composer. No network. No exploit.

Laravel's token guard used to authenticate a request when the credential was not a string. On MySQL and MariaDB that lookup can match a different user. The check that refuses a non-string token landed in August 2026. The advisory, GHSA-f9x3-7vq9-cph6 (CVE-2026-114509, CVSS 4.0 9.2), was published on 19 October. A composer.lock from September can still be on the wrong side of it.

Un fichier PHP. Zéro Composer. Aucun appel réseau. Aucun exploit.

Le token guard de Laravel acceptait une requête dont le jeton n'était pas une chaîne. Sur MySQL et MariaDB, la recherche peut alors tomber sur un autre utilisateur. Le contrôle qui refuse un jeton non-string est d'août 2026. L'avis, publié le 19 octobre, est GHSA-f9x3-7vq9-cph6 (CVE-2026-114509, CVSS 4.0 9.2). Un composer.lock de septembre peut encore être en dessous.

curl -fsSL -o tokengate.php \
  https://raw.githubusercontent.com/Nguemoue/project2026_20261030_tokengate/main/tokengate.php
php tokengate.php --self-test
php tokengate.php /path/to/your/laravel

The bug, precisely

TokenGuard loads the user with the credential it was given. Before the fix, the only gate was empty(). A non-string value can pass that and reach the query. The advisory says that under MySQL or MariaDB the query can match an existing user who was not the one the request named, on any route protected by that guard. Sanctum and Passport do not use this class.

The fix is commit 9b21ce0. user() continues only when is_string($token) && ! empty($token). validate() returns false unless the credential is a non-empty string. This tool does not show how to build the bad credential.

TokenGuard.php was compared on the framework tags, not only against the advisory sentence:

BranchString check present fromAdvisory's patched release
13.x13.27.0 (file identical in 13.27.0, 13.28.0 and 13.29.0)13.29.0
12.x12.68.012.68.0
11.x11.56.1not named; the advisory lists 12.68.0 and 13.29.0
10.x and oldernevernone (end of security support)

13.27 and 13.28 are not reported as critical: the guard file already matches 13.29.0. They are still behind the number the advisory tells you to install, so tokengate prints that and stays at medium. 12.67 and 11.56.0 do not have the check. 10.x never received it.

There is no workaround in the advisory. Updating the framework is the fix. Restart PHP-FPM, Octane and the queue workers after deploy, or they keep the old file in memory.

What a run looks like

tokengate 1.0.0  CVE-2026-114509
CRITICAL           exposed
  laravel/framework v12.40.2 is below the TokenGuard fix 12.68.0. Guard [api]
  uses driver "token". DB_CONNECTION is mysql (.env.example), which is the
  database named in the advisory.
  framework   v12.40.2  (composer.lock)
  token guard api  config/auth.php, hash false
  Update laravel/framework to 12.68.0 or later. The advisory lists no
  workaround. Restart PHP-FPM, Octane and queue workers afterwards so no
  process keeps the old file.
Exit 1: findings at or above high.

examples/exposed-12 is guilty on purpose. examples/patched-12 is the same guard on 12.68.0 and exits 0. examples/sanctum-old is an old 13.10 lock whose api guard is Sanctum: the token-guard bug is not that code path, so the default run does not fail. It still tells you the framework is below the fix.

The report names the guard, the file and the database driver. It does not read tokens out of .env and it does not print a request.

What it decides

SeverityVerdictWhat it means
criticalexposedThe installed tag has no string check, a guard uses driver => token, and DB_CONNECTION is mysql, mariadb, or missing.
highexposedSame, but the configured database is not MySQL or MariaDB. The published trigger is those two. The old guard is still the wrong code to ship.
highno-lock / unknown-version / version-and-unclear-guardLaravel is required, and tokengate cannot prove the fix is installed. A ^12.0 constraint is not a version. dev-master is not a version. env('API_DRIVER') with no default and no .env value hides the driver.
mediumunpatched-without-token-guardOld framework, but every guard driver found is a literal other than token (usually sanctum or session).
mediumguard-fixedThe string check is in this tag, and the tag is still below the advisory's number (13.27 and 13.28).
okpatched11.56.1+, 12.68.0+, or 13.29.0+.
oknot-laravellaravel/framework is not required.

Default CI fails on high. Medium is printed and does not fail unless you ask.

A cached bootstrap/cache/config.php wins over config/auth.php when tokengate can read it, because that is the config production actually booted.

Usage

php tokengate.php                      # the current directory
php tokengate.php /var/www/app
php tokengate.php --json               # stdout is JSON only
php tokengate.php --fail-on=medium     # also fail when the guard is absent but unused
php tokengate.php --fail-on=never      # always exit 0, still print the report
php tokengate.php --no-color
php tokengate.php --self-test          # built-in fixtures, no network

Exit 0 when nothing reaches the fail level (default: high). Exit 1 when something does. Exit 2 when the path or the flags are wrong.

PHP 8.1+ with the tokenizer extension, which PHP ships by default. The script tokenizes your config. It does not include it, so a dd() in config/auth.php does not run.

CI

- uses: shivammathur/setup-php@v2
  with:
    php-version: '8.3'
    coverage: none
- name: tokengate
  run: php tokengate.php --fail-on=high

Or, without adding the file to the app:

- name: tokengate
  run: |
      curl -fsSL -o /tmp/tokengate.php \
        https://raw.githubusercontent.com/Nguemoue/project2026_20261030_tokengate/main/tokengate.php
      php /tmp/tokengate.php .

php tokengate.php --self-test is the check for this repository, and it exits 0. Point the scanner at examples/exposed-12 when you want to see a failure.

Install

Copy the file. That is the supported install.

curl -fsSL -o tokengate.php \
  https://raw.githubusercontent.com/Nguemoue/project2026_20261030_tokengate/main/tokengate.php

composer.json is included so you can point a path repository at this git URL. The package is not required to be on Packagist.

What this is not

  • Not composer audit, and not a scan of the whole lockfile. One CVE, one class.
  • Not an exploit, a lab, or a request you can replay. If the tag is old and the token driver is on, the answer is to upgrade.
  • A guard registered only in a service provider, or built with a variable, is invisible. config/auth.php and bootstrap/cache/config.php are what get read.
  • Sanctum and Passport are out of scope. A hashed token ('hash' => true) still goes through TokenGuard, so it is still in scope.
  • It does not upload the project anywhere.

Le trou, en français

Le correctif est dans le code depuis le 25 août 2026 (Laravel 12.68.0 et 13.29.0). L'avis public est du 19 octobre. Entre les deux, beaucoup d'applications n'ont pas bougé : le tag dans composer.lock n'a pas changé, et le driver token dort encore dans config/auth.php depuis l'époque d'avant Sanctum.

Tu es concerné si les trois sont vrais :

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    627
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    416
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    379
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    330
  • 6

    Aliens_eye

    arxhr007/aliens_eye

    AI powered OSINT engine to discover and map 7,700+ social media identities across the web

    288

Explore all tools

Browse our collection of tools

View all tools →