https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-28T17:29:07.780700+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/cve-2026-47265 CVE-2026-47265 — AIOHTTP vulnerable to cross-origin redirect with per-request cookies 2026-09-28T17:29:07.785568+00:00

Affected: aio-libs aiohttp

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.14.0, 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. Version 3.14.0 patches the issue. If unable to upgrade, using a `Cookie` header in the `headers` parameter is not vulnerable.

 https://vulnerability.circl.lu/vuln/ghsa-hg6j-4rv6-33pg GHSA-hg6j-4rv6-33pg — AIOHTTP is vulnerable to cross-origin redirect with per-request cookies 2026-09-28T17:29:07.785671+00:00

Affected: PyPI: aiohttp

### 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

 https://vulnerability.circl.lu/vuln/pysec-2026-2105 PYSEC-2026-2105 2026-09-28T17:29:07.785730+00:00

Affected: PyPI: aiohttp

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.14.0, 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. Version 3.14.0 patches the issue. If unable to upgrade, using a `Cookie` header in the `headers` parameter is not vulnerable.