CVE-2026-68750
Quadratic-time HTML sanitizer flaw enables remote DoS via many sibling elements
Is CVE-2026-68750 being exploited?
Not confirmed. CVE-2026-68750 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.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-68750?
CVE-2026-68750 is rated High. 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-68750?
Yes. A fix has been recorded for CVE-2026-68750. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68750 affect?
CVE-2026-68750 affects html_sanitize_ex < 1.5.3, Elixir/Erlang web apps using html_sanitize_ex, Services exposing HTML sanitization entry points. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68750?
Upgrade to html_sanitize_ex >=1.5.3; enforce size/rate limits or WAF rules
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote attacker can exhaust CPU/memory (Denial of Service) by sending HTML with many sibling elements, degrading or crashing services.
Immediate action required
- affected>= 0.3.1 and < 1.4.5
- affected>= 1.5.0-rc.0 and < 1.5.3
- affected>= 69ea11d61525c470b39b6860d024770d5573ff1f and < *
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.