PatchSiren cyber security CVE debrief
CVE-2026-48500 filamentphp CVE debrief
CVE-2026-48500 is a medium-severity vulnerability in Filament, a collection of full-stack components for accelerated Laravel development. The vulnerability allows unauthenticated attackers to upload arbitrary files to the application's temporary storage, potentially exhausting disk space or inflating storage costs. This issue affects Filament versions from 3.0.0 until 3.3.52, 4.11.5, and 5.6.5. The vulnerability is fixed in versions 3.3.52, 4.11.5, and 5.6.5. The CVSS score for this vulnerability is 6.5, indicating a medium severity level. The vulnerability was published on June 22, 2026, and modified on June 23, 2026.
- Vendor
- filamentphp
- Product
- filament
- CVSS
- MEDIUM 6.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-22
- Original CVE updated
- 2026-06-23
- Advisory published
- 2026-06-22
- Advisory updated
- 2026-06-23
Who should care
Developers and administrators using Filament in their Laravel applications should be aware of this vulnerability and take necessary steps to mitigate it. This includes checking their current version of Filament and updating to a patched version if necessary. Additionally, users should be cautious of potential file upload vulnerabilities in their applications and implement proper security measures to prevent such attacks.
Technical summary
The vulnerability in Filament arises from the application of Livewire's WithFileUploads trait to Livewire components, even when file uploads are not required. This allows unauthenticated attackers to upload arbitrary files to the application's temporary storage. The vulnerability affects Filament versions from 3.0.0 until 3.3.52, 4.11.5, and 5.6.5. The CVSS vector for this vulnerability is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L, indicating a medium severity level. The weakness associated with this vulnerability is CWE-862.
Defensive priority
This vulnerability has a medium severity level and should be prioritized for remediation. Developers and administrators should take immediate action to update their Filament versions to 3.3.52, 4.11.5, or 5.6.5, or apply necessary patches to prevent exploitation.
Recommended defensive actions
- Update Filament to version 3.3.52, 4.11.5, or 5.6.5, or apply necessary patches.
- Implement proper security measures to prevent file upload vulnerabilities in applications.
- Monitor applications for potential file upload vulnerabilities and take necessary steps to mitigate them.
- Conduct regular security audits and vulnerability assessments to identify potential issues.
- Keep software and dependencies up-to-date with the latest security patches.
Evidence notes
The evidence for this vulnerability comes from the CVE record and the NVD detail page. The CVE record provides information on the vulnerability, including its description, CVSS score, and affected versions. The NVD detail page provides additional information, including the CVSS vector and weakness associated with the vulnerability. The source item URL provides further information on the vulnerability and its impact.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-48500 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-48500
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-48500 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-48500
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/filamentphp/filament/security/advisories/GHSA-44wp-g8f4-f4v5
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.