Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The aiohttp package is vulnerable before version 3.13.4. When a request follows a redirect to a different origin, aiohttp drops the Authorization header but keeps the Cookie and Proxy-Authorization headers, so those headers can be sent to an unintended party. The source gives few details about the attacker's position or required conditions. Upgrade to aiohttp 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:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0035, the 29th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 1 Apr 2026, 00:00 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-966j-vmvw-g2g9
- OSV: GHSA-966j-vmvw-g2g9
- github.com/aio-libs/aiohttp/security/advisories/GHSA-966j-vmvw-g2g9
- nvd.nist.gov/vuln/detail/CVE-2026-34518
- github.com/aio-libs/aiohttp/commit/5351c980dcec7ad385730efdf4e1f4338b24fdb6
- github.com/aio-libs/aiohttp
- github.com/aio-libs/aiohttp/releases/tag/v3.13.4