Self-checking PoC and Docker labs reproducing the Laravel TokenGuard array-token authentication bypass (CVE-2026-114509), with affected/fixed controls and a passive version scanner.
Disclaimer
Run
poc.pyonly against the included local labs. Runscan.pyonly against targets you are explicitly authorized to inspect. See AUTHORIZED_USE.md.
Laravel Framework 12.67.0 accepts an attacker-controlled JSON array as an API token. TokenGuard forwards [0] to Laravel's default Eloquent user provider, which builds api_token IN (0). MariaDB coerces a nonnumeric stored token to numeric zero, selects the victim row, and grants access to protected data. Laravel 12.68.0 rejects non-string tokens before the lookup.
The framework lab starts from the pinned laravel/laravel 12.12.2 application skeleton. It uses the normal application bootstrap, an Eloquent User, a migration and seeder, an api guard in config/auth.php, and auth:api route middleware. The protected endpoint is POST /api/account.


For HTTP assets, the scanner sends only bounded HEAD and GET requests to supplied URLs. The recorded demo uses the six loopback endpoints. A tcp:// asset receives a zero-byte connect and close. It does not run the PoC or test authentication bypass.
Run these commands from the repository root. You need Docker Engine with Compose v2 (up --wait), Python 3.10 or later, and free loopback ports 18080 through 18085. The PoC uses only the Python standard library.
For the Attendize event-management application:
docker compose -f lab/6.18.14/attendize/compose.yaml up -d --build --wait
python poc.py --profile attendize-6.18.14-mysql-5.7.44
python poc.py --profile attendize-6.18.14-local-backport-mysql-5.7.44
docker compose -f lab/6.18.14/attendize/compose.yaml down -v
For the real-application reproduction using Free PMO:
docker compose -f lab/8.83.27/free-pmo/compose.yaml up -d --build --wait
python poc.py --profile free-pmo-8.83.27-mariadb-11.4.8
python poc.py --profile free-pmo-8.83.27-local-backport-mariadb-11.4.8
docker compose -f lab/8.83.27/free-pmo/compose.yaml down -v
The smaller framework comparison lab remains available for an affected-versus-fixed control:
docker compose -f lab/12.67.0/laravel-token-guard/compose.yaml up -d --build --wait
python poc.py --profile laravel-12.67.0-mariadb-11.4.8
python poc.py --profile laravel-12.68.0-mariadb-11.4.8
docker compose -f lab/12.67.0/laravel-token-guard/compose.yaml down -v
The PoC first sends a wrong scalar token and requires 401. It then sends this JSON body:
{"api_token":[0]}
On affected builds, PASS requires the protected response. On each fixed control, PASS requires 401 for the same array token. The Attendize and Free PMO fixed controls are local backports of Laravel's string-type check to the pinned legacy dependency; they are not upstream fixed releases.
The released client accepts only the six shipped profiles and their fixed loopback URLs. It has no URL or path override. It does not scan, follow redirects, honor proxy environment variables, or accept public targets. Responses are limited to 1 MiB, and common credential fields are redacted from output.
Start all three Compose projects, then run the six-endpoint scan:
docker compose -f lab/12.67.0/laravel-token-guard/compose.yaml up -d --build --wait
docker compose -f lab/8.83.27/free-pmo/compose.yaml up -d --build --wait
docker compose -f lab/6.18.14/attendize/compose.yaml up -d --build --wait
python scan.py --assets assets.txt
python scan.py --assets assets.txt -v
python scan.py --assets assets.txt --format jsonl
python scan.py -u http://127.0.0.1:18080/
python scan.py -l assets.txt -t 4 -o scan-results.json
The -u, -l, -t, and -o flag names follow Assetnote's scanner CLI. They accept an explicit URL, a one-URL-per-line list, a requested worker count, and a JSON output file. --assets remains an alias for -l. At most 32 assets and four workers are used per run; larger -t values are capped. This scanner's JSON schema is its own: -o saves all result rows because AFFECTED_VERSION_OBSERVED reports a disclosed version, not a verified authentication bypass. The scanner accepts explicitly supplied HTTP(S) URLs outside loopback for authorized inventory work. It does not follow redirects or use proxy environment variables.
The default table shows each target and one icon under AFFECTED VERSION?:
✓ means an exact affected Laravel version was observed, ✗ means an exact
patched version was observed, and — means the version verdict is unknown.
Run with -v to see the full status, observed identity, HTTP detail, exposure,
signals, and elapsed time for every target. Verbose mode does not send extra
requests. JSON and JSONL always retain the full result fields.
The two Laravel skeleton roots show VERSION_HIDDEN because their welcome pages name Laravel without disclosing its version. The Free PMO and Attendize roots, including the local backports, redirect and show NO_FRAMEWORK_VERSION_EVIDENCE; their PHP version headers do not identify the Laravel dependency. These six roots therefore show — in the compact table. A version mentioned in an article does not count as runtime identity. None of these passive results confirms or rules out this CVE.
The Laravel identity regression ran twice with 11 labeled HTTP controls: TP=3, FP=0, TN=8, FN=0 for the claim “an affected Laravel version was explicitly disclosed.” It includes body-text decoys, hidden versions, redirects, a large response, and an outside-matrix version. These fixture counts do not measure exploitability or field accuracy.
Live tape · MP4 · raw terminal take · all-lab health record · labeled local controls
docker compose -f lab/6.18.14/attendize/compose.yaml down -v
docker compose -f lab/8.83.27/free-pmo/compose.yaml down -v
docker compose -f lab/12.67.0/laravel-token-guard/compose.yaml down -v