Skip to main content
VulnerabilityPublished

CVE-2026-128124: AIOHTTP · Event loop stall in add_domain() wildcard matching

Affects gamdlSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128124· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 4.0.0 soon.

Data as of 17 Nov 2026, 19:33 UTC

CVSS 4.0 base score
8.2High
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.08.2
Patch
Available – fixed in 4.0.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 16 Nov 2026.

What to do

Upgrade gamdl to 4.0.0.

Affected software

ProductAffectedFixed in
Homebrewgamdlpkg:brew/gamdlOther threatsAffected
  • >=3.9.1 <4.0.0
Fixed in
  • 4.0.0

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 AIOHTTP version 4.0.0 that fixes this issue. Users should upgrade to version 4.0.0 or later. As a temporary workaround, limit domain masks to at most one wildcard ('*').

Description

AIOHTTP's Application.add_domain() function had a performance issue where using two or more wildcards in a domain mask caused polynomial-time processing of long Host headers, leading to event loop stalls. This could allow an attacker to stall the server by sending requests with long Host headers against such domain masks. The issue affects versions from 3.9.1 up to but not including 4.0.0 and is fixed in version 4.0.0.

References

Community reviews

Loading reviews…