AI Threat Alert
Filamentphp
AI Threat Alert tracks 6 known AI/ML vulnerabilities affecting Filamentphp products — each enriched with CVSS severity, EPSS exploit probability, patch status, and CISO-grade analysis. Browse every Filamentphp CVE below, sorted by severity and recency.
| Severity | CVE | Headline | Package | CVSS |
|---|---|---|---|---|
| MEDIUM | CVE-2026-48067 | Filament: auth bypass via Livewire state tampering | 6.5 | |
| MEDIUM | CVE-2026-48500 | Filament: unauth file upload drains disk/inflates costs | 6.5 | |
| HIGH | CVE-2026-48505 | Filament: MFA race condition enables recovery code reuse | 7.4 | |
| MEDIUM | CVE-2026-48167 | Filament: stored XSS in ImageColumn/ImageEntry | 6.4 | |
| MEDIUM | CVE-2026-48166 | Filament: timing side-channel exposes registered emails | 5.3 | |
| HIGH | CVE-2026-55409 | Filament: stored XSS in disabled RichEditor field | 7.6 |
Frequently asked questions
How many known vulnerabilities affect Filamentphp?
6 AI/ML CVEs affecting Filamentphp products are tracked, sourced from NVD and GitHub Advisory.
What Filamentphp products are affected?
The CVEs below map to the Filamentphp AI/ML packages and tools tracked by AI Threat Alert; open any CVE to see the affected components and versions.
Where does the Filamentphp vulnerability data come from?
Data is sourced from NVD and GitHub Advisory, then enriched with CVSS severity, EPSS exploit probability, and patch status for each CVE.
How can I monitor Filamentphp for new vulnerabilities?
AI Threat Alert tracks Filamentphp continuously; a Pro subscription adds breaking alerts when new CVEs affecting Filamentphp are published.
How do I assess Filamentphp's security exposure?
Each CVE below carries CVSS severity and exploitation signals, so you can review the highest-severity Filamentphp issues first and judge the exposure for your stack.