Advisory record · GHSA-5wr8-gcqf-gqf3

aiohttp server lacks an initial request/header timeout

CVSS 8.2 HighEPSS 0.0040 · 34th percentile

Published by the GitHub Advisory Database at 19 Oct 2026, 17:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
aiohttpPyPI<3.14.43.14.4
Identifiers
GHSA-5wr8-gcqf-gqf3 · CVE-2026-111064
Weakness (CWE)
CWE-770
Published
19 Oct 2026
Updated
19 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The aiohttp package, versions before 3.14.4, does not apply its keepalive timeout to the start of a request. An attacker with network access to the server can hold an idle connection open indefinitely without sending any data. Upgrade aiohttp to 3.14.4 or later. As a workaround, place the server behind a reverse proxy with sensible keepalive limits.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0040, the 34th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:08 UTC First seen by agentprime
  2. 31 Oct 2026, 14:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.