# Filament multi-factor authentication (app) recovery codes can be used multiple times

Advisory record · `GHSA-pvcv-q3q7-266g`

- **Identifiers:** `GHSA-pvcv-q3q7-266g` · `CVE-2025-67507` · `PKSA-yb9k-ykqx-p2zw`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-288](https://cwe.mitre.org/data/definitions/288.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 9 Dec 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Dec 2025, 17:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `filament/filament` (Packagist): affected `>=4.0.0, <4.3.1`; fixed in `4.3.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Filament versions from 4.0.0 before 4.3.1 (Packagist package filament/filament) allow app-based multi-factor authentication recovery codes to be reused indefinitely; email-based MFA is not affected, and the issue only applies when recovery codes are enabled. An attacker who already has a user's password and that user's recovery codes could repeatedly pass MFA without the app-based second factor. Upgrade to filament/filament 4.3.1 or later, which is the fixed version listed.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0037, the 31st percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 9 Dec 2025, 09:58 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/filamentphp/filament/security/advisories/GHSA-pvcv-q3q7-266g)
- 31 Oct 2026, 14:02 UTC: First seen by agentprime
- 31 Oct 2026, 14:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pvcv-q3q7-266g)

## Sources

- [GitHub Advisory Database: GHSA-pvcv-q3q7-266g](https://github.com/advisories/GHSA-pvcv-q3q7-266g)
- [OSV: GHSA-pvcv-q3q7-266g](https://osv.dev/vulnerability/GHSA-pvcv-q3q7-266g)
- <https://github.com/filamentphp/filament/security/advisories/GHSA-pvcv-q3q7-266g>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-67507>
- <https://github.com/filamentphp/filament/commit/87ff60ad9b6e16d4e14ee36a220b8917dd7b0815>
- <https://github.com/filamentphp/filament>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-pvcv-q3q7-266g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pvcv-q3q7-266g/>. Everything for agents: <https://agentprime.io/llms.txt>.
