VulnerabilityPublished 13 Nov 2026

CVE-2026-126192: Soup Sieve · General sibling combinator inside :has() matches untrusted HTML in quadratic time

Affects jupyterlabSource GCVE Database

Compare

Authoritative record:CVE-2026-126192· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.6.4_1 when convenient.

Data as of 13 Nov 2026, 21:32 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 4.0	6.3

Patch: Available – fixed in 4.6.4_1

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade jupyterlab to 4.6.4_1.

Affected software

Product	Affected	Fixed in
Homebrewjupyterlab`pkg:brew/jupyterlab`Other threats	Affected >=3.3.2 <4.6.4_1	Fixed in 4.6.4_1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Soup Sieve version 4.6.4_1; users should upgrade to this version or later to resolve the issue. Additionally, users should avoid applying :has() selectors with general sibling combinators (~) on elements with many children, especially when processing untrusted HTML. Prefer using combinators like > or + inside :has() to limit traversal. If the risk is significant, input containing :has() selectors can be scanned and denied, or selector evaluation can be wrapped in timeouts to prevent long-running processes. These mitigations align with the vendor's guidance that quadratic time behavior is expected in some cases and careful use of :has() is recommended.

Description

Soup Sieve versions from 3.3.2 up to but not including 4.6.4_1 contain a performance vulnerability in the handling of selectors using a general sibling combinator inside :has(), such as div:has(a ~ b). This causes the selector evaluation against untrusted HTML to run in quadratic time relative to the number of sibling elements, potentially stalling processing for minutes on moderately sized inputs. The issue arises because the implementation cannot short-circuit when the sibling element is absent, leading to nested scans. This vulnerability impacts availability by enabling CPU exhaustion through crafted HTML inputs. A fix is available in version 4.6.4_1. Users are advised to limit the use of :has() with general sibling combinators on untrusted HTML and consider timeouts or input filtering to mitigate risk.

Impact

This vulnerability impacts availability by allowing an attacker to cause high CPU usage and stall the process that evaluates CSS selectors using :has() with a general sibling combinator on untrusted HTML input. The CPU time required grows quadratically with the number of sibling elements, making it feasible to cause delays of minutes with relatively small HTML inputs. This can lead to denial of service conditions in applications that process untrusted HTML with such selectors.

Summary

The vulnerability in Soup Sieve involves the use of a general sibling combinator (~) inside the :has() pseudo-class selector, e.g., div:has(a ~ b). When this selector is matched against untrusted HTML with many sibling elements, the evaluation runs in O(n²) time because the implementation performs nested scans for each candidate element without short-circuiting when the sibling is absent. This leads to significant CPU consumption and potential denial of service by stalling the process for minutes on inputs with a few thousand siblings. The adjacent sibling combinator (+) does not have this issue as it remains linear. The problem is inherent to the design of :has() but optimizations can reduce impact. The vulnerability affects Soup Sieve versions >=3.3.2 and <4.6.4_1, with a fix introduced in 4.6.4_1. The impact is availability degradation due to excessive CPU usage on crafted inputs. Mitigations include careful use of :has(), avoiding broad anchors with many children, preferring tighter combinators like > or + inside :has(), input filtering, and timeouts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 21:32 UTC

Technical details

References

Community reviews

Related threats