CVE-2026-126192: Soup Sieve · General sibling combinator inside :has() matches untrusted HTML in quadratic time
Affects enex2notionSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.3.1_25 when convenient.
Data as of 13 Nov 2026, 21:32 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 0.3.1_25
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation 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.
What to do
Upgrade enex2notion to 0.3.1_25.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewenex2notionpkg:brew/enex2notionOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch fixing this issue is available in enex2notion version 0.3.1_25 and should be applied. Users should also carefully design selectors using :has(), avoiding general sibling combinators (~) inside :has() on elements with many children. Prefer using adjacent sibling (+) or child (>) combinators inside :has() to limit traversal. If untrusted input must be processed, consider scanning for :has usage and denying such input or wrapping calls in timeouts to prevent long-running evaluations. Note that quadratic time complexity in some :has() scenarios is expected behavior, not a bug, so thoughtful selector design is the primary mitigation.
Description
CVE-2026-126192 is a performance-related vulnerability in Soup Sieve where using a general sibling combinator (~) inside the :has() CSS selector on untrusted HTML can cause quadratic time complexity. This can lead to significant CPU consumption and application stalls when processing HTML with many sibling elements. The issue arises because the selector evaluation performs nested scans without short-circuiting when the right-hand sibling is absent. The vulnerability affects versions >=0.2.17 and <0.3.1_25 of the product enex2notion. A fix is available in version 0.3.1_25. The impact is denial of service via high CPU usage, rated medium severity with a CVSS score of 6.3. Mitigations include careful use of :has() selectors, limiting the number of children on the anchor element, and preferring tighter combinators like > or + inside :has().
References
- github.com/facelessuser/soupsieve/security/advisories/GHSA-4j63-6c4x-wfg4 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-126192 (opens in a new tab)
- github.com/facelessuser/soupsieve/pull/304 (opens in a new tab)
- github.com/facelessuser/soupsieve/commit/ffb88cca745c591224f74a8e86414a85e8f35fc0 (opens in a new tab)
- github.com/facelessuser/soupsieve (opens in a new tab)
- github.com/facelessuser/soupsieve/releases/tag/2.10 (opens in a new tab)