# CVE-2026-34518: AIOHTTP leaks Cookie and Proxy-Authorization headers on cross-origin redirect

Source: https://junglewise.ai/threats/cve-2026-34518-aiohttp-leaks-cookie-and-proxy-authorization-headers-on-cross  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-01. Updated: 2026-05-11  
License: CC BY 4.0 with a link back

CVE-2026-34518 · Severity: medium · CVSS 5.3 · Published 2026-04-01

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, when following redirects to a different origin, aiohttp drops the Authorization header, but retains the Cookie and Proxy-Authorization headers. This issue has been patched in version 3.13.4.

Technologies: [Aiohttp](https://junglewise.ai/threats/technologies/aiohttp-aiohttp), [aiohttp (PyPI)](https://junglewise.ai/threats/technologies/aiohttp). Vendors: [Aiohttp](https://junglewise.ai/threats/vendors/aiohttp), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2026-34518 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-34518 being exploited in the wild.

**How severe is CVE-2026-34518?** Medium severity, with a CVSS score of 5.3, published 1 April 2026.

**Which products and versions are affected?** aiohttp (PyPI) <= 3.13.3, ECOSYSTEM:introduced=0,fixed=3.13.4.

**Is there a fix for CVE-2026-34518?** Yes. aiohttp (PyPI): upgrade to 3.13.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-34518?** Check whether you run Aiohttp or aiohttp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- aiohttp (PyPI): upgrade to 3.13.4 or later

  ```sh
  pip install "aiohttp>=3.13.4"
  ```


## Affected products

- Aiohttp
- aiohttp (PyPI) <= 3.13.3, ECOSYSTEM:introduced=0,fixed=3.13.4

## Identifiers

- CVE-2026-34518
- GHSA-966j-vmvw-g2g9
- PYSEC-2026-2100

## References

- [https://api.github.com/users/uug4na](https://api.github.com/users/uug4na)
- [https://github.com/uug4na](https://github.com/uug4na)
- [https://api.github.com/users/uug4na/gists%7B/gist_id%7D](https://api.github.com/users/uug4na/gists%7B/gist_id%7D)
- [https://api.github.com/users/uug4na/repos](https://api.github.com/users/uug4na/repos)
- [https://avatars.githubusercontent.com/u/65070195?v=4](https://avatars.githubusercontent.com/u/65070195?v=4)
- [https://api.github.com/users/uug4na/events%7B/privacy%7D](https://api.github.com/users/uug4na/events%7B/privacy%7D)

## Related threats

- [aiohttp HTTP request smuggling in pure Python parser](https://junglewise.ai/threats/cve-2026-111750-aiohttp-is-an-asynchronous-http-client-server-framework-for)
- [aiohttp host-only cookie scope bypass in subdomain handling](https://junglewise.ai/threats/cve-2026-111749-aiohttp-is-an-asynchronous-http-client-server-framework-for)
- [aiohttp Request scheme manipulation in absolute-form requests](https://junglewise.ai/threats/cve-2026-111748-aiohttp-is-an-asynchronous-http-client-server-framework-for)
- [AIOHTTP multipart request file descriptor exhaustion](https://junglewise.ai/threats/cve-2026-111066-aiohttp-is-an-asynchronous-http-client-server-framework-for)
- [aiohttp cookie Max-Age integer overflow causes connection pool exhaustion](https://junglewise.ai/threats/cve-2026-111065-aiohttp-is-an-asynchronous-http-client-server-framework-for)