CVE & CISA-KEV Catalog

CVE-2026-84306

MEDIUM
6.5
CVSS v3
NVD

Description

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.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityLow
AvailabilityNone

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploit Intelligence

0.36%probability of exploitation in 30 days
30thpercentile

Low risk: more likely to be exploited than 30% of all known CVEs.

References

Related Vulnerabilities

Other CWE-294 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2023-23397Critical9.897%KEVFix
CVE-2017-3191Critical9.863%--
CVE-2023-49231Critical9.843%--
CVE-2002-0054High7.522%--
CVE-2022-29593Medium5.914%--
CVE-2022-22806Critical9.812%--

Common questions

How do I fix CVE-2026-84306?

No published fix for CVE-2026-84306 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-84306 being actively exploited?

Not that we know of. CVE-2026-84306 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.36% is the estimated probability that it will be exploited in the next 30 days. That is higher than 30% of all scored CVEs.

How severe is CVE-2026-84306?

CVE-2026-84306 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-84306
CVE-2026-84306 severity badge

Markdown

[![CVE-2026-84306](https://tridentstack.com/cve/badge/CVE-2026-84306.svg)](https://tridentstack.com/cve/CVE-2026-84306)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-84306"><img src="https://tridentstack.com/cve/badge/CVE-2026-84306.svg" alt="CVE-2026-84306"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-09.