Intel

AIKIDO-2026-223593

html_sanitize_ex is vulnerable to Regular Expression Denial of Service (ReDoS)

CVE-2026-68749Published Aug 7, 2026
August 7, 2026

82

CVE Score

High

Regular Expression Denial of Service (ReDoS)

Are you affected? Scan for Free

TL;DR

The CSS scrubber matches a declaration's property name with an unbounded pattern followed by a mandatory colon, so a long run of word characters not followed by a colon forces the regex engine to backtrack one character at a time and retry from every offset. The work grows quadratically with the length of the run, and no length cap is applied to the CSS handed to the scrubber. Sanitizing a large style value therefore consumes seconds of scheduler time and can saturate the scheduler pool, making the application unresponsive. The fix bounds the matching so long non-declaration input no longer triggers quadratic backtracking.

How do I fix this?

Upgrade the html_sanitize_ex library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you sanitize content that reaches the CSS scrubber.

Versions

0.3.1 - 1.5.2

Fixed in 1.5.3

Background info

html_sanitize_ex is vulnerable to Regular Expression Denial of Service (ReDoS) in versions 0.3.1 - 1.5.2.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea