CVE-2026-49477: Soup Sieve: Regular Expression Denial of Service (ReDoS) in soupsieve Selector Parser

Published Jul 9, 2026
·
Updated

Summary

The CSS selector parser in soupsieve (the CSS selector engine for Beautiful Soup 4) contains a regular expression vulnerable to catastrophic backtracking. When processing an attribute selector with an unterminated quoted value, the VALUE regex pattern in cssparser.py enters exponential backtracking. A payload of only 300 bytes causes the regex engine to hang for over 3 seconds, enabling a trivial Regular Expression Denial of Service (ReDoS) attack.

To be completely transparent, AI tools helped surface this issue. However, this was independently reproduced and carefully validated.

Any application that passes untrusted CSS selector strings to soupsieve.compile() or Beautiful Soup's .select() / .selectone() is affected.

Details

Affected code: soupsieve/cssparser.py, line ~121 - REVALUES / VALUE regex pattern

The soupsieve CSS parser uses a compiled regular expression to tokenise attribute selector values. This pattern matches both quoted strings ("value" or 'value') and unquoted identifiers. The regex contains alternation branches for:

1. Double-quoted strings: "[^"\\](?:\\.[^"\\])" 2. Single-quoted strings: '[^'\\](?:\\.[^'\\])' 3. Unquoted identifiers

When an attribute selector contains an unterminated quoted value - e.g., [a="xxxx... (opening " but no closing ") -” the regex engine attempts to match the quoted-string branch. After that branch fails (no closing quote), the engine backtracks and attempts to match the remaining input against subsequent alternation branches and parent patterns. The structure of the pattern causes catastrophic backtracking where the number of backtracking steps grows exponentially with the length of the content between the opening quote and the end of the string.

Root cause: The regex pattern does not anchor or guard against the case where a quoted string is never terminated. The overlapping character classes across alternation branches create exponential backtracking when the quoted-string branch fails on long input.

Key characteristics: - Input size: Only 300 bytes are needed to trigger a >3 second hang - Amplification: Each additional character approximately doubles the backtracking time - No memory impact: The attack consumes CPU only (regex backtracking is compute-bound)

Proof of Concept

python import time import soupsieve as sv

PAYLOADLEN = 300

Control: well-formed selector with terminated quote (completes instantly) wellformed = '[a="' + ('x' PAYLOADLEN) + '"]' start = time.perfcounter() try: sv.compile(wellformed) except Exception: pass controltime = time.perfcounter() - start print(f"Well-formed selector ({len(wellformed)} bytes): {controltime:.4f}s")

Exploit: unterminated quote triggers catastrophic regex backtracking malformed = '[a="' + ('x' PAYLOADLEN) start = time.perfcounter() try: sv.compile(malformed) # WARNING: This will hang for >3 seconds except Exception: pass exploittime = time.perfcounter() - start print(f"Malformed selector ({len(malformed)} bytes): {exploittime:.4f}s")

slowdown = exploittime / max(controltime, 1e-9) print(f"Slowdown: {slowdown:.0f}x")

Expected output: Well-formed selector (306 bytes): ~0.001s Malformed selector (304 bytes): >3.0s (may need to be killed) Slowdown: >3000x NOTE: On some systems the malformed selector may hang indefinitely. Use a timeout mechanism (signal.alarm, threading.Timer) when testing.

Safe testing variant with timeout:

python import signal import soupsieve as sv

def timeouthandler(signum, frame): raise TimeoutError("ReDoS confirmed: regex backtracking exceeded timeout")

PAYLOADLEN = 300 malformed = '[a="' + ('x' PAYLOADLEN)

signal.signal(signal.SIGALRM, timeouthandler) signal.alarm(3) # 3-second timeout

try: sv.compile(malformed) print("Selector compiled (not vulnerable)") except TimeoutError as e: print(f"VULNERABLE: {e}") except Exception as e: print(f"Other error: {e}") finally: signal.alarm(0) # Cancel the alarm

Impact

Severity: High

An attacker can cause CPU exhaustion on any server-side Python application that compiles user-supplied CSS selectors via soupsieve. The attack is particularly dangerous because:

1. Tiny payload: Only 300 bytes are needed - well within typical URL parameter, form field, or API request limits 2. No special characters: The payload consists entirely of printable ASCII characters ([a="xxx...) 3. Exponential scaling: Each additional byte approximately doubles the backtracking time, making the attack easily tuneable 4. Thread blocking: The regex engine blocks the calling thread with no opportunity for interruption (except via OS signals)

| Parameter | Value | |---|---| | Input size | 300 bytes | | CPU time consumed | >3 seconds (exponential with payload length) | | Memory consumed | Negligible (CPU-only attack) | | Authentication required | None | | User interaction required | None |

Deployment impact: In threaded or async web applications, a single malicious request blocks a worker thread for the duration of the backtracking. An attacker can submit multiple concurrent requests to exhaust all available workers, causing complete service denial. The small payload size makes the attack easy to deliver and difficult to detect via request size limits.

Downstream exposure: soupsieve is an automatic dependency of beautifulsoup4, one of the most widely installed Python packages. Any web application, API, or service that accepts CSS selectors from users is potentially affected.

---

Credit

The vulnerability was discovered by a security research team from the University of Sydney, whose focus is detecting open source software vulnerabilities. Liyi Zhou: https://lzhou1110.github.io/ Ziyue Wang: https://zyy0530.github.io/ Strick: https://str1ckl4nd.github.io/ Maurice: https://maurice.busystar.org/ Chenchen Yu: https://7thparkk.github.io/

Other sources

Soup Sieve is a CSS selector library designed to be used with Beautiful Soup 4. Prior to 2.8.4, the CSS selector parser in soupsieve contains a regular expression vulnerable to catastrophic backtracking when processing an attribute selector with an unterminated quoted value in soupsieve/cssparser.py, allowing an attacker who can supply untrusted CSS selector strings to soupsieve.compile() or Beautiful Soup .select() / .selectone() to cause CPU exhaustion and denial of service. This issue is fixed in version 2.8.4.

— MITRE

Affected Software

2 affected componentsFixes available
pip/soupsieve<=2.8.3
2.8.4
facelessuser Soup Sieve Beautiful Soup<2.8.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/soupsieve to a version that resolves this vulnerability.

    Fixed in 2.8.4
  2. Upgrade

    Upgrade soupsieve/css_parser.py to a version that resolves this vulnerability.

    Fixed in 2.8.4

Event History

Jul 9, 2026
Advisory Published
via GitHub·01:37 PM
Data Sourced
via GitHub·01:37 PM
DescriptionSeverityWeaknessAffected Software
Jul 14, 2026
CVE Published
via MITRE·08:51 PM
Data Sourced
via MITRE·08:51 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·10:04 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-49477?

The severity of CVE-2026-49477 is high with a score of 7.5.

2

How do I fix CVE-2026-49477?

To fix CVE-2026-49477, update to the latest version of soupsieve available via pip.

3

What is the impact of CVE-2026-49477?

CVE-2026-49477 can lead to a denial of service due to catastrophic backtracking when processing certain CSS selectors.

4

Which software is affected by CVE-2026-49477?

CVE-2026-49477 affects the soupsieve library used in Beautiful Soup 4.

5

When was CVE-2026-49477 published?

CVE-2026-49477 was published on July 9, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203