Answer in brief
CVE-2026-63389 records a Medium severity (CVSS 5.0) vulnerability in Filament Curator: Cross-tenant media metadata disclosure via Curator picker search. The current sources do not mark it as known exploited. The current feed maps awcodes/filament-curator (composer), awcodes/filament-curator (composer), awcodes/filament-curator (composer), awcodes/filament-curator (composer) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps awcodes/filament-curator (composer), awcodes/filament-curator (composer), awcodes/filament-curator (composer), awcodes/filament-curator (composer) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| awcodes/filament-curatorcomposer | >=5.0.0,<5.1.1 | 5.1.1 |
| awcodes/filament-curatorcomposer | >=4.0.0,<4.1.1 | 4.1.1 |
| awcodes/filament-curatorcomposer | >=3.2.4,<3.7.8 | 3.7.8 |
| awcodes/filament-curatorcomposer | >=5.0.0,<5.1.1 | 5.1.1 |
| awcodes/filament-curatorcomposer | >=4.0.0,<4.1.1 | 4.1.1 |
| awcodes/filament-curatorcomposer | >=3.2.4,<3.7.8 | 3.7.8 |
| awcodes/filament-curatorpackagist | >=5.0.0 <5.1.1 | 5.1.1 |
| awcodes/filament-curatorpackagist | >=4.0.0 <4.1.1 | 4.1.1 |
| awcodes/filament-curatorpackagist | >=3.2.4 <3.7.8 | 3.7.8 |
Published upstream
Nov 17, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Nov 17, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Nov 17, 2026
Summary In multitenant Filament panels, an authenticated user could retrieve media metadata belonging to other tenants by typing in the Curator media-picker search box. The search query omitted the tenant ownership scope that the normal file listing applies. Details CuratorPanel::updatedSearch() built its Eloquent query independently of getFiles() and did not apply the filament()->hasTenancy() && $isTenantAware tenant-ownership where clause. As a result, the search matched media across all tenants. A secondary flaw compounded it: the orWhere('title'…) chain was not wrapped in a nested group, so the OR conditions also broke out of the isLimitedToDirectory constraint. The issue was introduced in v3.2.4, when multitenancy support was added to the media picker. Impact - Who: any authenticated user with access to a panel that uses the Curator picker. - What: disclosure of other tenants' media metadata (name, title, alt, caption, description, path, etc.) returned by the search. - Conditions: only affects deployments using Filament multitenancy with Curator's tenant awareness enabled. Single-tenant installs are not affected. Patches Fixed in 3.7.8, 4.1.1, and 5.1.1 by applying the tenant scope to the search query and grouping the search terms so they cannot escape the directory/tenant constraints. Upgrade to a patched version. Workarounds None other than upgrading. Disabling tenant awareness does not help (it removes the boundary entirely). Credit Reported via coordinated disclosure by [Afsana Alijabarova](https://github.com/afa114).
Quoted source text, attributed separately from HOL analysis.