CVE-2026-55409

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% 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.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.6Exploit: 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 3.0.0 until 3.3.53, a disabled RichEditor field rendered its raw state without sanitizing HTML. Where the data stored in this field's state isn't sanitized already when the form state was filled, an attacker could plant malicious HTML or JavaScript and achieve XSS that executes for users who view the form. This vulnerability is fixed in 3.3.53.

CVSS v3
7.6
EG Score
7.6(medium)
EPSS
6.5%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 23, 2026

Advisory Details (1)

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

Disabled RichEditor field state can be used for XSS · Advisory · filamentphp/filament · GitHub

https://github.com/filamentphp/filament/security/advisories/GHSA-m9cv-24rx-8mv7

Vendor Advisories for CVE-2026-55409(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)
PackageVulnerable rangeFixed inDependents
filament/formsv3.0.0 ... v3.3.9 (353 versions)3.3.53

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 54× 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 01:59 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 12:46 UTCEG score recompute
  5. 2026-07-05 23:32 UTCEG score recompute
  6. 2026-07-05 10:19 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 21:06 UTCEG score recompute
  10. 2026-07-04 07:53 UTCEG score recompute
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-03 18:27 UTCEG score recompute
  14. 2026-07-03 05:14 UTCEG score recompute
  15. 2026-07-02 16:01 UTCEG score recompute
  16. 2026-07-02 02:48 UTCEG score recompute
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-07-01 13:36 UTCEG score recompute
  19. 2026-07-01 00:23 UTCEG score recompute
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 11:08 UTCEG score recompute
  22. 2026-06-29 21:37 UTCEG score recompute
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 08:24 UTCEG score recompute
Show 29 more
  1. 2026-06-28 19:11 UTCEG score recompute
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 05:58 UTCEG score recompute
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 16:45 UTCEG score recompute
  7. 2026-06-27 03:32 UTCEG score recompute
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 14:18 UTCEG score recompute
  10. 2026-06-26 01:05 UTCEG score recompute
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-25 11:51 UTCEG score recompute
  13. 2026-06-24 22:38 UTCEG score recompute
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-24 09:25 UTCEG score recompute
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-23 20:13 UTCEG score recompute
  19. 2026-06-23 06:57 UTCEG score recompute
  20. 2026-06-22 17:42 UTCEG score recompute
  21. 2026-06-22 04:30 UTCEG score recompute
  22. 2026-06-21 15:17 UTCEG score recompute
  23. 2026-06-21 02:03 UTCEG score recompute
  24. 2026-06-20 12:51 UTCEG score recompute
  25. 2026-06-19 23:35 UTCEG score recompute
  26. 2026-06-19 10:23 UTCEG score recompute
  27. 2026-06-18 21:09 UTCEG score recompute
  28. 2026-06-18 07:56 UTCEG score recompute
  29. 2026-06-17 18:44 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55409?
CVE-2026-55409 is a high vulnerability published on June 17, 2026. Filament is a collection of full-stack components for accelerated Laravel development. From 3.0.0 until 3.3.53, a disabled RichEditor field rendered its raw state without sanitizing HTML. Where the data stored in this field's state isn't sanitized already when the form state was filled, an attacker…
When was CVE-2026-55409 disclosed?
CVE-2026-55409 was first published in the National Vulnerability Database on June 17, 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-55409 actively exploited?
CVE-2026-55409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55409?
CVE-2026-55409 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-55409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55409, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55409

Explore →

Is Your Infrastructure Affected by CVE-2026-55409?

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