CVE-2026-47265: AIOHTTP vulnerable to cross-origin redirect with per-request cookies

Published Jun 2, 2026
·
Updated

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

Other sources

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.

NVD

Affected Software

4 affected componentsFixes available
pypi/aiohttp<3.14.0
pip/aiohttp<3.14.0
3.14.0
aiohttp aiohttp<3.14.0
IBM API Connect<=V10.0.8.0 - V10.0.8.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.0
  2. Upgrade

    Upgrade aio-libs/aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.0Patch f54c40851b0d6c4bbdab97ba518a223adda32478
  3. Configuration

    If unable to upgrade to 3.14.0, avoid using the per-request `cookies` parameter; instead set the `Cookie` header via the `headers` parameter to prevent sending cookies after a cross-origin redirect.

    aiohttp cookies parameter vs Cookie header = Use Cookie header in headers parameter instead of cookies parameter on a per-request basis

Event History

Jun 2, 2026
CVE Published
via MITRE·06:32 PM
Data Sourced
via MITRE·06:32 PM
DescriptionWeakness
Data Sourced
via NVD·08:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 3, 2026
Advisory Published
via GitHub·09:34 PM
Data Sourced
via GitHub·09:34 PM
DescriptionWeaknessAffected Software
Jul 7, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-47265?

CVE-2026-47265 has a severity score of medium (6.6) according to the CVSS version 4.0.

2

How does CVE-2026-47265 affect AIOHTTP applications?

CVE-2026-47265 allows sensitive data from per-request cookies to be sent after following cross-origin redirects, potentially exposing this information.

3

How do I fix CVE-2026-47265?

To remediate CVE-2026-47265, upgrade AIOHTTP to version 3.14.0 or later.

4

What versions of AIOHTTP are affected by CVE-2026-47265?

CVE-2026-47265 affects all versions of AIOHTTP prior to version 3.14.0.

5

Is CVE-2026-47265 a critical vulnerability?

CVE-2026-47265 is not considered critical, but it poses risks due to the potential exposure of sensitive data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203