CVE-2026-48505

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.11.5 and 5.6.5, a flaw in the handling of recovery codes for app-based multi-factor authentication allows the same recovery code to be reused via concurrent submission. This issue does not affect email-based MFA. It also only applies when recovery codes are enabled. If an attacker gains access to both the user's password and their recovery codes, they get two authenticated sessions per recovery code burned instead of one, or more if they batch the parallel submissions wider, materially extending the attacker's window of access compared to what the single-use guarantee implies. This vulnerability is fixed in 4.11.5 and 5.6.5.

CVSS v3
7.4
EG Score
7.4(medium)
EPSS
9.2%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 23, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
github Patch Available

Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission · Advisory · filamentphp/filament · GitHub

https://github.com/filamentphp/filament/security/advisories/GHSA-mc5j-f6wx-h9qh

Vendor Advisories for CVE-2026-48505(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 47× 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.

  1. 2026-07-07 06:00 UTCEG score recompute
  2. 2026-07-06 18:45 UTCEG score recompute
  3. 2026-07-06 06:37 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 19:26 UTCEG score recompute
  6. 2026-07-05 08:15 UTCEG score recompute
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 21:04 UTCEG score recompute
  9. 2026-07-04 09:53 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-03 22:36 UTCEG score recompute
  12. 2026-07-03 11:25 UTCEG score recompute
  13. 2026-07-03 00:05 UTCEG score recompute
  14. 2026-07-02 12:52 UTCEG score recompute
  15. 2026-07-02 01:42 UTCEG score recompute
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 14:30 UTCEG score recompute
  18. 2026-07-01 03:19 UTCEG score recompute
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 16:08 UTCEG score recompute
  21. 2026-06-30 04:56 UTCEG score recompute
  22. 2026-06-29 17:28 UTCEG score recompute
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 06:15 UTCEG score recompute
Show 22 more
  1. 2026-06-28 19:01 UTCEG score recompute
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 07:50 UTCEG score recompute
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 20:39 UTCEG score recompute
  7. 2026-06-27 09:29 UTCEG score recompute
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 22:18 UTCEG score recompute
  10. 2026-06-26 11:07 UTCEG score recompute
  11. 2026-06-25 19:15 UTCEG score recompute
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-25 08:04 UTCEG score recompute
  14. 2026-06-24 20:52 UTCEG score recompute
  15. 2026-06-24 14:05 UTCEPSS rescore
  16. 2026-06-24 09:41 UTCEG score recompute
  17. 2026-06-23 22:28 UTCEG score recompute
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-23 11:16 UTCEG score recompute
  21. 2026-06-23 00:04 UTCEG score recompute
  22. 2026-06-23 00:00 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48505?
CVE-2026-48505 is a high vulnerability published on June 22, 2026. Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.11.5 and 5.6.5, a flaw in the handling of recovery codes for app-based multi-factor authentication allows the same recovery code to be reused via concurrent submission. This issue does not…
When was CVE-2026-48505 disclosed?
CVE-2026-48505 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48505 actively exploited?
CVE-2026-48505 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48505?
CVE-2026-48505 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-48505?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48505, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48505

Explore →

Is Your Infrastructure Affected by CVE-2026-48505?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs