AIOHTTP is vulnerable to cross-origin redirect with per-request cookies
Published 3 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected aiohttp?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <3.14.0
- Fixed in
- 3.14.0
pip install 'aiohttp>=3.14.0'Details
Summary
Cookies set with the cookies parameter on requests are sent after following a cross-origin redirect.
Impact
If a developer uses the cookies parameter on a per-request basis then sensitive data might be leaked to an attacker if they manage to control a redirect.
Workaround
If unable to upgrade, using a Cookie header in the headers parameter is not vulnerable.
-----
Patch: https://github.com/aio-libs/aiohttp/commit/f54c40851b0d6c4bbdab97ba518a223adda32478
Is GHSA-hg6j-4rv6-33pg in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected aiohttp, and gives you the command that fixes it.
More advisories for aiohttp
- HighCVE-2026-128124AIOHTTP: Event loop stall in add_domain() wildcard matching · 16 Nov 2026
- MediumCVE-2026-128125AIOHTTP: Unbounded cookie storage in client CookieJar · 16 Nov 2026
- HighCVE-2026-128126AIOHTTP: Too many URL-encoded form fields block the event loop · 16 Nov 2026
- HighCVE-2026-128127AIOHTTP: Base64 multipart parts bypass client_max_size · 16 Nov 2026
- HighCVE-2026-128128AIOHTTP: WebSocket max_msg_size bypass via integer overflow · 16 Nov 2026
- HighCVE-2026-128129AIOHTTP: Unbounded buffering of data received during an upgrade request · 16 Nov 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.