CVE-2026-85999: Soup Sieve: Polynomial-time ReDoS (O(n²)) in the whitespace/comment trimming regex `RE_WS_END` (triggers on VALID selectors)
Soup Sieve is a CSS selector library designed to be used with Beautiful Soup 4. Prior to 2.9, selectoriter in src/soupsieve/cssparser.py trims the raw selector with REWSEND, an end-anchored WSC whitespace-and-comment expression used with search(), so the regular expression engine retries a greedy scan at every starting offset. An attacker-controlled valid selector containing a long internal whitespace run, or a selector containing a long CSS comment run followed by another token, causes quadratic CPU work before tokenization. User-controlled selectors can reach the path through soupsieve.compile() and BeautifulSoup.select(), while applications using only hard-coded selectors are unaffected. This root cause is separate from the IDENTIFIER and VALUE backtracking vulnerability because the cost occurs in REWSEND.search during trimming rather than token matching. The resulting CPU consumption can hold the Python GIL, exhaust workers, and stall a service without causing memory corruption or code execution. The issue is fixed in version 2.9.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
soupsieveto a version that resolves this vulnerability.Fixed in 2.9
Event History
Frequently Asked Questions
Which applications are exposed to this issue?
Applications are exposed when untrusted users can supply CSS selectors that reach soupsieve.compile() or BeautifulSoup.select(). Applications that use only hard-coded selectors are unaffected.
What selector input can trigger the CPU exhaustion?
A valid attacker-controlled selector with a long internal whitespace run can trigger quadratic processing. A selector with a long CSS comment run followed by another token can also trigger it.
What is the practical impact of exploitation?
Processing the selector can consume CPU while holding the Python GIL, potentially exhausting workers and stalling the service. The issue does not cause memory corruption or code execution.
What should be done to remediate the issue?
Upgrade Soup Sieve to version 2.9, which fixes the issue.