VulnerabilityPublished 13 Nov 2026

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

Affects gimme-aws-credsSource GCVE Database

Compare

Authoritative record:CVE-2026-126192· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.8.2_16 when convenient.

Data as of 13 Nov 2026, 21:54 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 2.8.2_16

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 gimme-aws-creds to 2.8.2_16.

Affected software

Product	Affected	Fixed in
Homebrewgimme-aws-creds`pkg:brew/gimme-aws-creds`Other threats	Affected >=2.3.3_1 <2.8.2_16	Fixed in 2.8.2_16

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

AI-suggested

A fix is available in Soup Sieve version 2.8.2_16. Users should upgrade to this version or later to resolve the issue. Additionally, users should carefully design selectors using :has() to avoid general sibling combinators (~) inside it when processing untrusted HTML. Prefer using combinators like adjacent sibling (+) or child (>) inside :has() to limit traversal. If risk remains high, input containing :has selectors can be denied or selector evaluation wrapped in timeouts to prevent long-running processes. Quadratic time complexity is expected behavior for some :has() selectors, so thoughtful use is recommended.

Description

CVE-2026-126192 describes a performance issue in Soup Sieve when using a CSS selector with a general sibling combinator inside :has(), such as div:has(a ~ b). This selector runs in quadratic time relative to the number of sibling elements when matched against untrusted HTML, causing significant CPU delays. The issue arises because Soup Sieve performs nested scans for each candidate element, leading to O(n²) complexity. This can stall applications processing attacker-controlled HTML. The vulnerability is mitigated by careful selector design and is fixed in version 2.8.2_16.

Impact

The vulnerability impacts availability by allowing an attacker to cause high CPU usage and stall applications that evaluate selectors containing a general sibling combinator inside :has() over untrusted HTML. This can lead to denial of service conditions with relatively small HTML inputs containing thousands of sibling elements. The issue arises from the quadratic time complexity of the selector evaluation algorithm in these cases.

Summary

Soup Sieve's implementation of the :has() pseudo-class combined with the general sibling combinator (~) can cause quadratic time complexity when matching selectors like div:has(a ~ b) against untrusted HTML. The selector asks whether an element contains an 'a' element with a later sibling 'b'. When no 'b' is present, Soup Sieve performs a nested scan over siblings, resulting in O(n²) comparisons. This leads to CPU usage increasing quadratically with the number of sibling elements, demonstrated by a proof-of-concept where processing 8000 siblings takes nearly a minute. The adjacent sibling combinator (+) does not exhibit this issue as it only checks the immediate next sibling. This behavior is inherent to the selector's design and not unique to Soup Sieve. The impact is a denial of service via CPU exhaustion when processing attacker-controlled HTML with such selectors. The issue is fixed in Soup Sieve version 2.8.2_16.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats