filament/filament

CVE-2026-48500

CVE-2026-48500 is a medium-severity missing authorization vulnerability in filament/filament (composer), affecting versions >= 4.0.0, <= 4.11.4. It is fixed in 4.11.5, 5.6.5, 3.3.52.

Key facts
CVSS score
6.5
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
filament/filament
Fixed in
4.11.5, 5.6.5, 3.3.52
Disclosed
2026

Summary

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.

Impact

What is missing authorization?

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Severity and exposure

CVE-2026-48500 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (4.11.5, 5.6.5, 3.3.52). Upgrading removes the vulnerable code path.

Affected versions

composer

  • filament/filament (>= 4.0.0, <= 4.11.4)
  • filament/filament (>= 5.0.0, <= 5.6.4)
  • filament/filament (>= 3.0.0, <= 3.3.51)

Security releases

  • filament/filament → 4.11.5 (composer)
  • filament/filament → 5.6.5 (composer)
  • filament/filament → 3.3.52 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-48500 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-48500 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-48500 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade filament/filament to 4.11.5 or later
  • Upgrade filament/filament to 5.6.5 or later
  • Upgrade filament/filament to 3.3.52 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-48500

What is CVE-2026-48500?

CVE-2026-48500 is a medium-severity missing authorization vulnerability in filament/filament (composer), affecting versions >= 4.0.0, <= 4.11.4. It is fixed in 4.11.5, 5.6.5, 3.3.52. The application does not perform an authorization check before performing a sensitive operation.

How severe is CVE-2026-48500?

CVE-2026-48500 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of filament/filament are affected by CVE-2026-48500?

filament/filament (composer) versions >= 4.0.0, <= 4.11.4 is affected.

Is there a fix for CVE-2026-48500?

Yes. CVE-2026-48500 is fixed in 4.11.5, 5.6.5, 3.3.52. Upgrade to this version or later.

Is CVE-2026-48500 exploitable, and should I be worried?

Whether CVE-2026-48500 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-48500 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-48500?
  • Upgrade filament/filament to 4.11.5 or later
  • Upgrade filament/filament to 5.6.5 or later
  • Upgrade filament/filament to 3.3.52 or later

Stop the waste.
Protect your environment with Kodem.