Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
aiohttp versions before 3.13.4 do not limit the number of trailer headers they accept, so an attacker who can send a request or response can cause uncapped memory usage and possibly memory exhaustion in the application. The source says a typical reverse proxy configuration can mitigate the risk. Upgrade to aiohttp 3.13.4.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.9 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0046, the 40th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Mar 2026, 23:57 UTC Published by the maintainers as a GitHub repository advisory
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-w2fm-2cpv-w7v5
- OSV: GHSA-w2fm-2cpv-w7v5
- github.com/aio-libs/aiohttp/security/advisories/GHSA-w2fm-2cpv-w7v5
- nvd.nist.gov/vuln/detail/CVE-2026-22815
- github.com/aio-libs/aiohttp/commit/0c2e9da51126238a421568eb7c5b53e5b5d17b36
- github.com/aio-libs/aiohttp
- github.com/aio-libs/aiohttp/releases/tag/v3.13.4