CVE-2026-63389: Filament Curator · Cross-tenant media metadata disclosure via Curator picker search
Affects awcodes/filament-curatorSource GCVE Database
Not known to be exploited · CVSS 5.0 Medium : upgrade to 5.1.1 when convenient.
Data as of 17 Nov 2026, 21:52 UTC
- Patch
- Available – fixed in 5.1.1, 4.1.1, 3.7.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade awcodes/filament-curator to 5.1.1; awcodes/filament-curator to 4.1.1; awcodes/filament-curator to 3.7.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistawcodes/filament-curator | Affected
| Fixed in
|
| Packagistawcodes/filament-curator | Affected
| Fixed in
|
| Packagistawcodes/filament-curator | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected versions to 3.7.8, 4.1.1, or 5.1.1 or later, where the tenant scope is correctly applied to the search query and search terms are properly grouped to enforce tenant boundaries. No other workarounds are available; disabling tenant awareness removes tenant boundaries entirely and is not recommended.
Description
In multitenant deployments of the Filament Curator media picker, an authenticated user could retrieve media metadata belonging to other tenants due to improper tenant ownership scoping in search queries. This vulnerability affects versions from 3.2.4 up to but not including 3.7.8, 4.1.1, and 5.1.1. The flaw was fixed by applying tenant scope correctly and grouping search terms to enforce tenant and directory constraints. Only multitenant setups with tenant awareness enabled are affected; single-tenant installations are not vulnerable.
References
- github.com/awcodes/filament-curator/security/advisories/GHSA-828w-6qgx-3rcf (opens in a new tab)
- github.com/awcodes/filament-curator/commit/17615a20924b7cd373595f6ec56abb79f23cdf7f (opens in a new tab)
- github.com/awcodes/filament-curator/commit/c129a3692d7ef1c9923a2be7402704b20ed4f243 (opens in a new tab)
- github.com/awcodes/filament-curator (opens in a new tab)
- github.com/awcodes/filament-curator/releases/tag/v3.7.8 (opens in a new tab)
- github.com/awcodes/filament-curator/releases/tag/v4.1.1 (opens in a new tab)
- github.com/awcodes/filament-curator/releases/tag/v5.1.1 (opens in a new tab)