Is jayanta/laravel-threat-detection vulnerable?

Composer jayanta/laravel-threat-detection has 4 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

4advisories

0critical

0on CISA KEV

0no fix recorded

CVE	Title	Severity	Affected	Fixed in
2026-09-06-1	Plaintext credentials written to the threat log and readable by any authenticated user	unknown	`<1.8.0`	`1.8.0`
2026-09-29-1	Attacks go unrecorded when a request carries malformed headers or oversized fields	unknown	`<1.9.0`	`1.9.0`
2026-09-29-2	Marking a detection as a false positive could create a wider exclusion rule than intended	unknown	`<1.9.0`	`1.9.0`
2026-09-29-3	Credentials under prefixed or nested names stored in cleartext in the threat log	unknown	`<1.9.0`	`1.9.0`

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.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   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

A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.