Vulnerability in filament/filament (CVE-2026-104181)
Summary
Vulnerability in filament/filament (CVE-2026-104181). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.8.3 or later.
Original description
The description as published by the source.
App-based multi-factor authentication management actions did not consistently require the user to confirm their current password. In particular, an authenticated session could set up app-based MFA and obtain recovery codes without password reauthentication. Disabling app-based MFA and regenerating recovery codes also accepted an existing app code or recovery code without requiring the current password. This issue does not affect email-based MFA.
If an attacker gains access to a user's authenticated session, they could enable app-based MFA and obtain recovery codes without knowing the user's password, changing the account's MFA configuration and potentially locking the legitimate user out. This issue does not by itself allow an unauthenticated attacker to sign in.
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-104181 has been found in filament/filament.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade filament/filament to 5.8.3 or later.
If unsure, ask your IT team or search "filament/filament CVE-2026-104181" on the vendor's site.
CVE-2026-104181 (filament/filament) — CWE-306 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.8.3 — 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-306) exists in filament/filament.
Check the vendor advisory for the affected versions of filament/filament.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 5.8.3.
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.8.3ステージング環境で 5.8.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。