Skip to main content
Menu
CVEs

CVE

aiohttp denial of service in add_domain() wildcard matching

Only affects aiohttp servers that register a domain mask with more than one wildcard via Application.add_domain(). Fixed in 3.14.4.

CVE-2026-128124EUVD-2026-125754

Written by a model from the sources below. Verify against them.

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

8.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.14.4
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Server registers a domain mask with more than one wildcard via Application.add_domain()

Published
Last modified
Reference
Last checked
0.52% · 44th percentile
20/100
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

AIOHTTP, an asynchronous HTTP client and server framework for Python, is affected when a server uses `add_domain()` with a domain mask containing two or more wildcards. A remote attacker, without logging in, can repeatedly send crafted Host headers that take a long time to reject and stall the server's event loop.

Original description

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Application.add_domain() converts every asterisk wildcard in a domain mask into a greedy regular-expression fragment, so a mask containing two or more wildcards can take polynomial time to reject a long Host header that does not match. A remote attacker can repeatedly send such headers to a server configured with a multi-wildcard domain mask and stall the event loop. This issue is fixed in version 3.14.4.

Who should check

Teams running aiohttp 3.14.3 or earlier whose server registers an Application.add_domain() mask with more than one wildcard

“registers a domain mask with more than one wildcard”

github.com

cve.now Index

20cve.now Index 20 of 100 · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.2/10CVSS 8.2
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    Server registers a domain mask with more than one wildcard via Application.add_domain()
  • Upgrade to a fixed version: 3.14.4.

  • Workaround: Use at most one * in a domain mask.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128124 (AIOHTTP: Event loop stall in add_domain() wildcard matching), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128124 (entry last updated 2026-11-13):
Affected:
- aio-libs aiohttp: fixed in 3.14.4
Fixed versions: 3.14.4.
Vendor patches: c6ac0e4 (source: https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jm3w-gw2p-xjfj). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Server registers a domain mask with more than one wildcard via Application.add_domain() (source: https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jm3w-gw2p-xjfj)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
Workaround: Use at most one * in a domain mask. (source: https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jm3w-gw2p-xjfj)
CISA KEV: CVE-2026-128124 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128124 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jm3w-gw2p-xjfj
- https://github.com/aio-libs/aiohttp/pull/13943
- https://github.com/aio-libs/aiohttp/pull/13945
- https://github.com/aio-libs/aiohttp/commit/766b882820da0651c84090e366a3b024b4a263c9
- https://github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43
- https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128124
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128124"}.

Public exploit activity

100%0Nov 13Nov 18
  • EPSS: 0.52%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • aio-libs aiohttp

    fixed in 3.14.4

Evidence 8

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Repository
  2. Repository
  3. Repository
  4. Repository
  5. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-128124

Is CVE-2026-128124 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A server that registers a domain mask with more than one wildcard can have its event loop stalled by requests carrying a long, non-matching Host header, which causes a denial of service.Source: github.com

Which versions are affected by CVE-2026-128124?

aiohttp: before 3.14.4.Source: cve.now feed data

Am I affected, and how do I check?

Affected setups are aiohttp versions before 3.14.4 whose application registers a domain mask with more than one * wildcard through Application.add_domain(). To check, look at the aiohttp version installed and search the application code for add_domain() calls using masks with more than one *.Source: github.com

How do I fix CVE-2026-128124?

Upgrade aiohttp to 3.14.4 or later, which contains the fix (patch c6ac0e4). Until then, use at most one * in a domain mask.Source: github.com

More CVEs