Vulnerability in filament/filament (CVE-2026-48505)
Summary
Vulnerability in filament/filament (CVE-2026-48505). Confidential information can be exposed externally. Mitigation: upgrade to 5.6.5 or later.
Original description
The description as published by the source.
A flaw in the handling of recovery codes for app-based multi-factor authentication allows the same recovery code to be reused via concurrent submission. This issue does not affect email-based MFA. It also only applies when recovery codes are enabled.
If an attacker gains access to both the user's password and their recovery codes, they get two authenticated sessions per recovery code burned instead of one, or more if they batch the parallel submissions wider, materially extending the attacker's window of access compared to what the single-use guarantee implies.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48505 has been found in filament/filament.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade filament/filament to 5.6.5 or later.
If unsure, ask your IT team or search "filament/filament CVE-2026-48505" on the vendor's site.
CVE-2026-48505 (filament/filament) — CWE-362 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.6.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-362) exists in filament/filament.
Check the vendor advisory for the affected versions of filament/filament.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 5.6.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'filament/filament' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'filament/filament' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
filament/filamentを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade filament/filament to 5.6.5ステージング環境で 5.6.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com