aiohttp server lacks initial request and header timeout
Summary
In aiohttp, the keepalive timeout was not applied during the initial portion of a request.
Impact
An attacker can keep an idle connection open indefinitely prior to transmitting any data, potentially tying up server resources.
Workaround
Deploy a reverse proxy with sensible keepalive limits in front of the application, as recommended for all production deployments.
What to do
Upgrade to aiohttp version 3.14.4 or later. If upgrading is not immediately possible, use a reverse proxy with sensible keepalive limits.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | aiohttp | < 3.14.4 | 3.14.4 |
References
- CVSS vector
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- Weakness (CWE)
CWE-770- Platform
- Python (PyPI)
- Package
aiohttp- Disclosed
- 19.10.2026
- Updated
- 20.10.2026 10:51
Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.
OSV / GitHub Advisory Database - GHSA-5wr8-gcqf-gqf3 - CC BY 4.0
Vulnerability history: aiohttp
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 55
- First → latest
- 02.2021 10.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 7
- Medium 29
- Low 19
Disclosures per year
- 2021: 1
- 2022: 0
- 2023: 6
- 2024: 7
- 2025: 1
- 2026: 40
-
aiohttp server lacks initial request and header timeout this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.