# CVE-2026-48500: Filament: Unauthenticated temporary file upload on auth pages

> Unauthenticated attackers can upload arbitrary files to temporary storage, potentially exhausting disk space or inflating costs.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-44wp-g8f4-f4v5

## What is CVE-2026-48500?

CVE-2026-48500 is a medium-severity vulnerability in filamentphp filament, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Filament is a collection of full-stack components for accelerated Laravel development. From 3.0.0 until 3.3.52, 4.11.5, and 5.6.5, any schema can contain a file upload form field, so Filament applies Livewire's WithFileUploads trait to the Livewire component the schema is embedded in. However, some schemas, such as the panel login form, do not require file uploads, and exposing unauthenticated temporary file uploads on these components is not an acceptable risk. On these components, an unauthenticated attacker could upload arbitrary files to the application's temporary storage, which could be abused to exhaust disk space or inflate storage costs. This vulnerability is fixed in 3.3.52, 4.11.5, and 5.6.5.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-48500?

6 open source packages ship an affected version, including filament/filament.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `filament/filament` | Packagist | From 3.0.0 | 3.3.52 |
| `filament/filament` | Packagist | From 3.0.0 | 3.3.52 |
| `filament/filament` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/filament` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/filament` | Packagist | From 5.0.0 | 5.6.5 |
| `filament/filament` | Packagist | From 5.0.0 | 5.6.5 |

## How do I fix CVE-2026-48500?

Upgrade filament/filament to a fixed version for your release line: 3.3.52, 4.11.5 or 5.6.5.

## Is CVE-2026-48500 being exploited?

There is no known exploitation of CVE-2026-48500 in the wild and no public exploit code.

Public exploit code:

- https://github.com/rimbadirgantara/CVE-2026-48500 (github_poc): https://github.com/rimbadirgantara/CVE-2026-48500

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48500 and fix it if it is affected.

What it is: CVE-2026-48500 is a medium-severity vulnerability in filamentphp filament, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48500 in the wild and no public exploit code.

Affected packages and fixed versions:
- filament/filament (Packagist): affected from 3.0.0; fixed in 3.3.52
- filament/filament (Packagist): affected from 3.0.0; fixed in 3.3.52
- filament/filament (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/filament (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.6.5
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.6.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48500/ (Markdown: https://insights.sbomify.com/CVE-2026-48500/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48500
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48500
- OSV: https://osv.dev/vulnerability/CVE-2026-48500

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48500/
Summaries are generated and may contain mistakes; the official description above is the record.