CVE-2026-68749: rrrene html_sanitize_ex ReDoS in CSS scrubber

CVE-2026-68749 · Severity: high · CVSS 7.5 · Published 2026-08-06

html_sanitize_ex is a library used to clean potentially malicious HTML and CSS before display in web applications. An attacker can send carefully crafted CSS with very long declaration names to trigger exponential processing time in the CSS validation logic, causing the application server to consume all available CPU and become unresponsive to legitimate requests.

Technologies: Rrrene Html Sanitize Ex, Rrrene Htmlsanitizeex. Vendors: Rrrene.

Quick answers

Is CVE-2026-68749 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-68749 being exploited in the wild.
How severe is CVE-2026-68749?
High severity, with a CVSS score of 7.5, published 6 August 2026.
Which products and versions are affected?
Rrrene Html Sanitize Ex 0.3.1 to <1.4.5 and 1.5.0-rc.0 to <1.5.3.
Is there a fix for CVE-2026-68749?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-68749 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-68749?
Check whether you run Rrrene Html Sanitize Ex or Rrrene Htmlsanitizeex at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

This is a Regular Expression Denial of Service (ReDoS) vulnerability in the CSS property regex matcher within HtmlSanitizeEx.Scrubber.CSS.scrub/1. The vulnerable regex uses an unbounded greedy quantifier ([-\w]+) followed by a mandatory colon, causing catastrophic backtracking when matching a long run of word characters not followed by a colon. The regex engine tries matching at every offset, resulting in quadratic time complexity relative to CSS length. An unauthenticated attacker can send an 80 KB CSS declaration that consumes ~2.4 seconds of CPU per request; multiple concurrent requests saturate the BEAM scheduler and render the application unresponsive. No data exfiltration or code execution occurs; impact is CPU exhaustion only.

Affected products

  • rrrene html_sanitize_ex 0.3.1 to <1.4.5 and 1.5.0-rc.0 to <1.5.3

Timeline

  • 2026-08-06: disclosed
  • 2026-08-06: advisory: CVE-2026-68749 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.