facil.io 0.6.0 through 0.7.6 contains a denial-of-service vulnerability in the multipart body parser that allows an unauthenticated remote attacker to permanently freeze worker processes at 100% CPU by sending a multipart/form-data request with a partial closing boundary. The missing progress guard in the parser loop causes http_mime_parse to return 0 bytes consumed without setting done or error flags, causing the calling loop to re-invoke the parser on the same buffer indefinitely, exhausting all workers and permanently disabling the server until manually restarted.
CVE-2026-66730
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-27. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 27, 2026
Last Modified
July 27, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026facil.io 0.6.0 - 0.7.6 Infinite Loop DoS via Multipart MIME Body Parser | Advisories | VulnCheck
https://www.vulncheck.com/advisories/facil-io-infinite-loop-dos-via-multipart-mime-body-parserGitHub - theopaid/Infinite-Loop-DoS-in-facil.io-MIME-Parser: Security Advisory: Infinite Loop DoS in facil.io MIME Parser (Partial Boundary) · GitHub
https://github.com/theopaid/Infinite-Loop-DoS-in-facil.io-MIME-ParserVendor Advisories for CVE-2026-66730(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× 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-07-28 07:21 UTCGHSA enrichment
- 2026-07-27 19:30 UTCEG score recompute
- 2026-07-27 19:30 UTCGHSA enrichment
- 2026-07-27 19:06 UTCEG score recompute
- 2026-07-27 19:06 UTCGHSA enrichment
- 2026-07-27 17:19 UTCEG score recompute
- 2026-07-27 17:00 UTCEG score recompute
- 2026-07-27 17:00 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-835
Frequently asked(4)
What is CVE-2026-66730?
When was CVE-2026-66730 disclosed?
What is the CVSS score of CVE-2026-66730?
How do I remediate CVE-2026-66730?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66730
Is Your Infrastructure Affected by CVE-2026-66730?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.