CVE-2026-47265Medium▾ SunlitAIOHTTP is vulnerable to cross-origin redirect with per-request cookies
▾ Sunlit zone — Low / medium · no exploitation signal
impact 27.5 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 30.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
0.1%
Last analysed / modified upstream
0.1% → 0.2%
Cookies set with the cookies parameter on requests are sent after following a cross-origin redirect.
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.
If unable to upgrade, using a Cookie header in the headers parameter is not vulnerable.
Patch: https://github.com/aio-libs/aiohttp/commit/f54c40851b0d6c4bbdab97ba518a223adda32478
aiohttp < 3.14.0Upgrade to a patched release:
aiohttp 3.14.0Connected by shared product, vendor, weakness, or advisory.
CVE-2026-111065Medium· 6.9AIOHTTP: Connector pool exhaustion via Max-Age overflow
CVE-2026-111748Medium· 6.3AIOHTTP: Absolute-form request targets can spoof Request.scheme
CVE-2026-111749Low· 2.3AIOHTTP: Cookie from subdomain can remove Host-Only Scope from existing cookies
CVE-2026-111750Medium· 6.3AIOHTTP: Pure-Python parser request smuggling
GHSA-2g87-pp6c-29x5Highaiohttp: Multiple instances of excessive or unbounded memory/CPU use
CVE-2026-111063Medium· 6.3AIOHTTP: Secure attribute not enforced for shared cookie