2026-09-29-2: Marking a detection as a false positive could create a wider exclusion rule than intended

unknown Affects jayanta/laravel-threat-detection. Feed 2026.10.29.1, updated 2026-10-28.

Marking a detection as a false positive could create a wider exclusion rule than intended

Package: jayanta/laravel-threat-detection Composer
Affected versions: <1.9.0
Fixed in: 1.9.0
Severity: unknown
Exploitation: not on CISA KEV
Source: friendsofphp

References

https://github.com/jay123anta/laravel-threat-detection/security/advisories/GHSA-rppj-hxxm-v5pr

NVD record jayanta/laravel-threat-detection advisories

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs How findings are ranked

Related advisories

2026-09-06-1 unknown Plaintext credentials written to the threat log and readable by any authenticated user same package: jayanta/laravel-threat-detection
2026-09-29-1 unknown Attacks go unrecorded when a request carries malformed headers or oversized fields same package: jayanta/laravel-threat-detection
2026-09-29-3 unknown Credentials under prefixed or nested names stored in cleartext in the threat log same package: jayanta/laravel-threat-detection