Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The aiohttp package, versions before 3.13.4, is affected. Its C parser (llhttp) accepted null bytes and control characters in request header values, so an attacker who can send crafted HTTP requests may get headers interpreted differently than intended, which could enable a security bypass. The source gives few details on the exact bypass scenario. Upgrade aiohttp to version 3.13.4 or later.
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 |
|---|---|---|---|---|
| 2.7 | Low | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0048, the 41st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 1 Apr 2026, 00:01 UTC Published by the maintainers as a GitHub repository advisory
- 31 Oct 2026, 14:34 UTC First seen by agentprime
- 31 Oct 2026, 14:34 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-63hf-3vf5-4wqf
- OSV: GHSA-63hf-3vf5-4wqf
- github.com/aio-libs/aiohttp/security/advisories/GHSA-63hf-3vf5-4wqf
- nvd.nist.gov/vuln/detail/CVE-2026-34520
- github.com/aio-libs/aiohttp/commit/9370b9714a7a56003cacd31a9b4ae16eab109ba4
- github.com/aio-libs/aiohttp
- github.com/aio-libs/aiohttp/releases/tag/v3.13.4
- github.com/pypa/advisory-database/tree/main/vulns/aiohttp/PYSEC-2026-2102.yaml