# CVE-2026-104181: Filament: Multi-factor authentication (app) management actions do not require password reauthentication

> Authenticated attackers can modify app-based MFA settings without password reauthentication, potentially locking out legitimate users or bypassing security controls.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-7m6h-rg42-m449

## What is CVE-2026-104181?

CVE-2026-104181 is a medium-severity missing authorization vulnerability in filamentphp filament, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.13.3 and 5.8.3, app-based multi-factor authentication management actions do not consistently require confirmation of the current password. An attacker with access to an authenticated user session can set up app-based MFA and obtain recovery codes, or disable app-based MFA and regenerate recovery codes by supplying an existing app code or recovery code, without knowing the account password. Email-based MFA is not affected, and the issue does not independently permit an unauthenticated sign-in, but changing the app-MFA configuration may lock the legitimate user out. This issue is fixed in versions 4.13.3 and 5.8.3.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-104181?

4 open source packages ship an affected version, including filament/filament.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `filament/filament` | Packagist | From 4.0.0 | 4.13.3 |
| `filament/filament` | Packagist | From 4.0.0 | 4.13.3 |
| `filament/filament` | Packagist | From 5.0.0 | 5.8.3 |
| `filament/filament` | Packagist | From 5.0.0 | 5.8.3 |

## How do I fix CVE-2026-104181?

Upgrade filament/filament to a fixed version for your release line: 4.13.3 or 5.8.3.

## Is CVE-2026-104181 being exploited?

There is no known exploitation of CVE-2026-104181 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104181 and fix it if it is affected.

What it is: CVE-2026-104181 is a medium-severity missing authorization vulnerability in filamentphp filament, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104181 in the wild and no public exploit code.

Affected packages and fixed versions:
- filament/filament (Packagist): affected from 4.0.0; fixed in 4.13.3
- filament/filament (Packagist): affected from 4.0.0; fixed in 4.13.3
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.8.3
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.8.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104181/ (Markdown: https://insights.sbomify.com/CVE-2026-104181/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104181
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104181
- OSV: https://osv.dev/vulnerability/CVE-2026-104181

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104181/
Summaries are generated and may contain mistakes; the official description above is the record.