Skip to main content
VulnerabilityPublished Updated

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

Affects knot-resolverSource GCVE Database

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

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

Data as of 18 Nov 2026, 18:21 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 6.5.0_1
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 knot-resolver to 6.5.0_1.

Affected software

ProductAffectedFixed in
Homebrewknot-resolverpkg:brew/knot-resolverOther threatsAffected
  • >=6.1.0 <6.5.0_1
Fixed in
  • 6.5.0_1

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 Knot resolver version 6.5.0_1 that addresses this issue. Users should upgrade to this version to remediate the vulnerability. As a workaround, deploying a reverse proxy with appropriate keepalive timeout limits is recommended and advised for all production environments.

Description

Knot resolver's aiohttp server did not apply a keepalive timeout during the initial request phase, allowing an attacker to keep an idle connection open indefinitely before sending data. This vulnerability affects versions from 6.1.0 up to but not including 6.5.0_1. A fix is available in version 6.5.0_1. The recommended workaround is to use a reverse proxy with sensible keepalive limits, which is advised for all production deployments.

References

Community reviews

Loading reviews…