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

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, aiohttp (PyPI). Vendors: Aiohttp, 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
    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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.