Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.12.6 and 5.7.6, packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php uses AppAuthentication::verifyCode() with a used-code cache key derived from both the app authentication secret and the submitted TOTP code. This isolates the newest accepted timestep by code instead of by secret, allowing a previously issued app-based MFA code to be accepted after a newer code has already been used. Reuse of the exact same code was already prevented, but another code inside the accepted time window remained usable. An attacker who obtains the target account's password and one app-based MFA code can use that code for the remainder of the configured window, which is approximately four minutes with the default settings, even after the legitimate account holder logs in with a newer code. Email-based MFA is not affected. This issue is fixed in versions 4.12.6 and 5.7.6.
CVE-2026-84306
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
September 1, 2026
Last Modified
September 9, 2026
Advisory Details (5)
Auto-updated Sep 1, 2026Multi-factor authentication (app) codes can still be used after a newer code has been used · Advisory · filamentphp/filament · GitHub
https://github.com/filamentphp/filament/security/advisories/GHSA-r3j6-gpjw-qfjrv5.7.6
Patch available: filamentphp/filament v5.7.6
https://github.com/filamentphp/filament/releases/tag/v5.7.6v4.12.6
Patch available: filamentphp/filament v4.12.6
https://github.com/filamentphp/filament/releases/tag/v4.12.6fix: Cache used MFA codes using hash of secret rather than secret and code
Patch available: filamentphp/filament v4.12.6 (PR #20335 merged 2026-08-05)
https://github.com/filamentphp/filament/pull/20335commit b6bde8572bca (filamentphp/filament)
Patch available: filamentphp/filament v4.12.6 (contains commit b6bde8572bca)
https://github.com/filamentphp/filament/commit/b6bde8572bcac75d4f5b4ec892ba7b9e91e0ab4dVendor Advisories for CVE-2026-84306(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| filament/filament | v5.0.0 ... v5.7.5 (44 versions) | 5.7.6 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 32× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 03:33 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 05:25 UTCEG score recompute
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 07:16 UTCEG score recompute
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 09:06 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 10:10 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 11:59 UTCEG score recompute
- 2026-09-12 15:41 UTCEG score recompute
- 2026-09-11 17:32 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 19:22 UTCEG score recompute
- 2026-09-08 23:22 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 20:04 UTCEG score recompute
- 2026-09-06 21:54 UTCEG score recompute
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-05 23:40 UTCEG score recompute
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 01:32 UTCEG score recompute
Show 7 moreShow fewer
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-04 03:23 UTCEG score recompute
- 2026-09-04 02:34 UTCEG score recompute
- 2026-09-02 17:53 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 19:18 UTCEG score recompute
- 2026-09-01 19:17 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-84306?
When was CVE-2026-84306 disclosed?
Is CVE-2026-84306 actively exploited?
What is the CVSS score of CVE-2026-84306?
How do I remediate CVE-2026-84306?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84306
Is Your Infrastructure Affected by CVE-2026-84306?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.