Servers and applications
GHSA-h2hg-mfj4-rg7q
`in` / `Rule::in` validation rule bypass via loose comparison
- Severity
- Medium 5.3
- Published
- 18 Nov 2026
- Last changed
- 18 Nov 2026
- Added to UpHeron
- 18 Nov 2026
- Fixed in
- 12.67.0, 13.26.0
- Weakness
- Incorrect comparison (CWE-697)
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N- Sources
- Project advisories (GitHub)
Description
The in validation rule (and Rule::in, and not_in via the same code) compares the scalar input to the allowlist with a non-strict in_array(). PHP 8 then compares numeric strings numerically, so many values that are not literally in the list pass validation — including whitespace-padded, leading-zero, signed, and scientific-notation forms, and an embedded newline. The value returned by validated() / valid() is the raw, un-canonicalized input, so the attacker-controlled bytes flow through to the application even though the rule was supposed to constrain them to a fixed set.
The array branch of the same method already compares as strings (array_diff), so this is an internal inconsistency, not intended behavior.
Any allowlist of numeric values — feature flags (in:0,1), status codes, role/tenant/enum IDs stored as integers may be bypassed with an equivalent-but-not-identical representation.
— Sergey Sannikov, GitHub @semx
Affected software
| Software | Affected versions |
|---|---|
LaravelServers and applications · github:laravel/framework |
|
About Laravel
open source web application framework, written in PHP
- Developers who used it in the past year
- 8.9%Stack Overflow Developer Survey 2025, 2025
- Monthly downloads (Packagist)
- 24,524,463Packagist, 15 Nov 2026
- Total downloads (Packagist)
- 622,287,963Packagist, 15 Nov 2026
- GitHub stars
- 35,000GitHub, 15 Nov 2026
- Forks
- 12,030GitHub, 15 Nov 2026
- Latest release
- v13.42.0GitHub, 15 Nov 2026
- Released
- 10 Nov 2026GitHub
- Developer
- Taylor OtwellWikidata
- License
- MIT LicenseWikidata
- Written in
- PHPWikidata
- First released
- 9 Jun 2011Wikidata
- First published on GitHub
- 10 Jan 2013GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 13 | 13.42.0 | Until 17 Mar 2028 |
| 12 | 12.72.0 | Until 24 Feb 2027 |
| 11 | 11.57.1 | Ended 12 Mar 2026 |
| 10 | 10.50.4 | Ended 4 Feb 2025 |
| 9 | 9.52.23 | Ended 6 Feb 2024 |
| 8 | 8.83.29 | Ended 24 Jan 2023 |
From endoflife.date.
Vulnerabilities in Laravel
- In our list
- 32
- Published in the last 12 months
- 26
- Critical, last 12 months
- 1
- High, last 12 months
- 1
- Known exploited
- 0
- GHSA-ww2c-pqp9-rvrqCross-Origin Auth Token Leakage Through Broadcasting JSONP CallbackLow 3.1 18 Nov 2026
- GHSA-ch34-gjmh-c4hpFluent Rule::exists() and Rule::unique() where() values can be interpreted as reserved predicates instead of literal valuesMedium 4.8 18 Nov 2026
- GHSA-h84h-g58v-xg2hQuadratic regex backtracking in the decimal validation rule can cause denial of serviceMedium 5.3 18 Nov 2026
- GHSA-wwq3-m3j5-wv66Validation exists rule can be bypassed with integer or boolean input on MySQL/MariaDBMedium 5.3 18 Nov 2026
- GHSA-f3ph-5p6j-34xrNested sometimes validation rules skipped when value is __missing__Medium 6.5 18 Nov 2026
- GHSA-cgwv-q695-mj8gUnbounded $ref chain resolution in Illuminate\JsonSchema\Deserializer allows denial of serviceMedium 5.3 18 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-h2hg-mfj4-rg7q
- github.com https://github.com/laravel/framework/security/advisories/GHSA-h2hg-mfj4-rg7q