Skip to main content
VulnerabilityPublished Updated

CVE-2026-111064: Ansible@12 · aiohttp server lacks an initial request/header timeout

Affects ansible@12Source GCVE Database

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

Not known to be exploited · CVSS 8.2 High.

Data as of 18 Nov 2026, 18:48 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
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

Affected software

ProductAffectedFixed in
Homebrewansible@12pkg:brew/ansible%4012Other threatsAffected
  • >=12.3.0_1
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 in front of the Ansible@12 aiohttp server with configured sensible keepalive timeout limits to prevent idle connections from persisting indefinitely. This workaround is recommended by the vendor and aligns with best practices for production environments.

Description

Ansible@12's aiohttp server does not enforce a timeout during the initial request or header phase, allowing an attacker to keep an idle connection open indefinitely before sending any data. This can lead to resource exhaustion on the server. The vulnerability affects versions starting from 12.3.0_1. A recommended mitigation is to deploy a reverse proxy with appropriate keepalive timeout settings.

References

Community reviews

Loading reviews…