Skip to main content
VulnerabilityPublished Updated

CVE-2026-111064: Dnstwist · aiohttp server lacks an initial request/header timeout

Affects dnstwistSource GCVE Database

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

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

Data as of 18 Nov 2026, 18: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 20250130_14
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 19 Oct 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 17 Nov 2026.

What to do

Upgrade dnstwist to 20250130_14.

Affected software

ProductAffectedFixed in
Homebrewdnstwistpkg:brew/dnstwistOther threatsAffected
  • >=20220815 <20250130_14
Fixed in
  • 20250130_14

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 dnstwist version 20250130_14 that addresses this issue. If you cannot patch yet, deploying a reverse proxy with sensible keepalive timeout limits is recommended as a workaround. This is the advised approach for all production deployments.

Description

The aiohttp server component used by dnstwist did not enforce a keepalive timeout during the initial request phase, allowing an attacker to keep an idle connection open indefinitely without sending data. This vulnerability can lead to resource exhaustion by holding connections open unnecessarily. A fix is available in version 20250130_14. The recommended mitigation is to deploy a reverse proxy with appropriate keepalive limits, which is advised for all production environments.

References

Community reviews

Loading reviews…