Skip to main content
VulnerabilityPublished Updated

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

Affects rawdogSource GCVE Database

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

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

Data as of 18 Nov 2026, 18:03 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 0.1.6_29
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 rawdog to 0.1.6_29.

Affected software

ProductAffectedFixed in
Homebrewrawdogpkg:brew/rawdogOther threatsAffected
  • >=0.1.5 <0.1.6_29
Fixed in
  • 0.1.6_29

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 Rawdog version 0.1.6_29 that addresses this issue. Users should upgrade to this version or later. Additionally, deploying a reverse proxy with appropriate keepalive timeout settings is recommended as a workaround to limit idle connections.

Description

Rawdog's aiohttp server did not enforce 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 0.1.5 up to but not including 0.1.6_29. A fix is available in version 0.1.6_29. Using a reverse proxy with proper keepalive limits is recommended as a workaround.

References

Community reviews

Loading reviews…