Skip to main content
VulnerabilityPublished Updated

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

Affects aiderSource 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, 20:25 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
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Homebrewaiderpkg:brew/aiderOther threatsAffected
  • >=0.47.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 with sensible keepalive timeout limits in front of the aiohttp server, as recommended by the vendor. This workaround helps mitigate the risk by enforcing connection timeouts externally.

Description

The aiohttp server component in the Aider product 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 and denial of service conditions. The vulnerability affects versions 0.47.1 and later. A workaround is to use a reverse proxy with appropriate keepalive limits, as recommended for production deployments. The CVSS 4.0 score is 8.2, indicating a high severity issue.

References

Community reviews

Loading reviews…