Is CVE-2026-104181 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-104181 being exploited in the wild.

How severe is CVE-2026-104181?

Medium severity, with a CVSS score of 5.4, published 1 October 2026.

Which products and versions are affected?

Filament 4.0.0 to 4.13.2, 5.0.0 to 5.8.2; filament/filament (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.13.3.

Is there a fix for CVE-2026-104181?

Yes. filament/filament (Packagist): upgrade to 4.13.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-104181 attacked?

It is attacked from the adjacent network.

Am I affected by CVE-2026-104181?

Check whether you run Filament or filament/filament (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-104181: Filament multi-factor authentication bypass without password

CVE-2026-104181 · Severity: medium · CVSS 5.4 · Published 2026-10-01

Filament is a Laravel development framework that includes multi-factor authentication (MFA) management features for user account security. An attacker who gains access to an authenticated user's session can configure app-based MFA, disable it, or regenerate recovery codes without requiring the user's password, potentially locking the legitimate user out of their account. The vulnerability does not enable unauthenticated login, but significantly weakens account security for already-compromised sessions.

Technologies: Filament, filament/filament (Packagist). Vendors: Filament, Packagist.

Quick answers

Is CVE-2026-104181 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-104181 being exploited in the wild.
How severe is CVE-2026-104181?: Medium severity, with a CVSS score of 5.4, published 1 October 2026.
Which products and versions are affected?: Filament 4.0.0 to 4.13.2, 5.0.0 to 5.8.2; filament/filament (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.13.3.
Is there a fix for CVE-2026-104181?: Yes. filament/filament (Packagist): upgrade to 4.13.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-104181 attacked?: It is attacked from the adjacent network.
Am I affected by CVE-2026-104181?: Check whether you run Filament or filament/filament (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

filament/filament (Packagist): upgrade to 4.13.3 or later
```
composer require filament/filament:^4.13.3
```

Technical details

The app-based MFA management actions in Filament versions 4.0.0–4.13.2 and 5.0.0–5.8.2 lack consistent password confirmation checks before allowing modification of MFA settings. An attacker with an active authenticated session can supply an existing app code or recovery code to set up new MFA, disable existing MFA, or regenerate recovery codes without password verification. Email-based MFA is not affected. The fix adds password verification to these sensitive actions.

Affected products

Filament Filament 4.0.0 to 4.13.2, 5.0.0 to 5.8.2

Identifiers

CVE-2026-104181
GHSA-7m6h-rg42-m449

Timeline

2026-10-01: disclosed
2026-09-18: patched: Fix commit merged

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.