UBUNTU-CVE-2026-126189: Medium severity ubuntu/soupsieve vulnerability

Published Nov 13, 2026
·
Updated

Soup Sieve is a CSS selector library designed to be used with Beautiful Soup 4. Prior to 4.0.1, Soup Sieve repeatedly searches descendant subtrees for each candidate evaluated by :has() and repeatedly reevaluates a parent containing :has(> ...) for each child, causing quadratic matching on deeply nested or wide attacker-influenced HTML or XML. Applications using ordinary fixed selectors through select(), selectone(), or Beautiful Soup CSS APIs against untrusted documents can have a worker occupied for seconds or minutes, while applications that process only trusted documents are not affected. Selectors compiled with NOCACHE continue to use the old uncached behavior. This issue is fixed in version 4.0.1.

Affected Software

5 affected components
ubuntu/soupsieve*
ubuntu/soupsieve*
ubuntu/soupsieve*
ubuntu/soupsieve*
ubuntu/soupsieve*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.0.1

Event History

Nov 13, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which applications are realistically exposed to this issue?

Applications that use Soup Sieve CSS selection APIs, including select(), select_one(), or Beautiful Soup CSS APIs, against attacker-influenced HTML or XML are exposed. Processing only trusted documents is not affected.

2

Does exploitation require an attacker to control the CSS selector?

No. Ordinary fixed selectors can be affected when they are applied to untrusted documents. The attacker needs to provide crafted deeply nested or wide HTML or XML that triggers costly :has() matching behavior.

3

What is the operational impact of a successful attack?

An attacker can cause quadratic selector matching that occupies a worker for seconds or minutes. The stated impact is availability degradation rather than confidentiality or integrity loss.

4

Are all selector compilation modes fixed by upgrading?

Version 4.0.1 fixes the issue, but selectors compiled with NOCACHE continue to use the old uncached behavior. Review whether the application explicitly compiles selectors with NOCACHE.

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