CVE-2026-111064: Ansible@13 · aiohttp server lacks an initial request/header timeout
Affects ansible@13Source GCVE Database
Not known to be exploited · CVSS 8.2 High.
Data as of 17 Nov 2026, 18:50 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.2 |
|---|
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewansible@13pkg:brew/ansible%4013Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Use a reverse proxy with sensible keepalive timeout limits as a workaround.
Description
Ansible version 13 and later using aiohttp server lacks an initial request/header timeout, allowing an attacker to keep an idle connection open indefinitely before sending any data. This can lead to resource exhaustion on the server. A reverse proxy with sensible keepalive limits is recommended as a workaround.
References
- github.com/aio-libs/aiohttp/security/advisories/GHSA-5wr8-gcqf-gqf3 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/be846822b4b3a5a54b6163e794b42dc06fba54a3 (opens in a new tab)
- github.com/aio-libs/aiohttp (opens in a new tab)
- github.com/aio-libs/aiohttp/releases/tag/v3.14.4 (opens in a new tab)