Skip to content
Web

CVE-2026-66730

8.7
High
EPSS 0.60%Jul 28, 2026

Unauthenticated multipart parser DoS freezes workers at 100% CPU.

common questions

Is CVE-2026-66730 being exploited?

Not confirmed. CVE-2026-66730 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.60% probability of exploitation in the next 30 days.

How severe is CVE-2026-66730?

CVE-2026-66730 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-66730?

Not known from our data. No patch reference has been recorded for CVE-2026-66730, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-66730 affect?

CVE-2026-66730 affects facil.io 0.6.0 - 0.7.6, Applications using facil.io HTTP multipart parser. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-66730?

Apply vendor patch when released; block/inspect multipart/form-data; restart workers if impacted.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
facil.io 0.6.0 - 0.7.6Applications using facil.io HTTP multipart parser
impact

Unauthenticated attacker sends a crafted multipart/form-data with a partial closing boundary causing http_mime_parse to loop and freeze workers at 100% CPU, resulting in permanent DoS until manual restart.

action required

Immediate action required

affected versions
boazsegev facil.io
  • affected>= 0.6.0 and <= 0.7.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free