Quick answers
- Is CVE-2026-111063 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111063 being exploited in the wild.
- How severe is CVE-2026-111063?
- Low severity, published 19 October 2026.
- Which products and versions are affected?
- Aio-Libs Aiohttp before 3.14.4; aiohttp (PyPI) <= 3.14.3, ECOSYSTEM:introduced=0,fixed=3.14.4.
- Is there a fix for CVE-2026-111063?
- Yes. aiohttp (PyPI): upgrade to 3.14.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111063 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-111063?
- Check whether you run Aio-Libs 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.14.4 or later
pip install "aiohttp>=3.14.4"
Technical details
AIOHTTP does not properly enforce the Secure cookie attribute, allowing cookies intended for HTTPS-only transmission to be sent over plain HTTP. This is a cookie handling vulnerability in the framework's HTTP client/server implementation. An attacker can exploit this by downgrading the connection or intercepting traffic to capture cookies marked Secure.
Affected products
- aio-libs AIOHTTP before 3.14.4
Identifiers
- CVE-2026-111063
- GHSA-494j-54xm-rwp3
Timeline
- 2026-10-19: disclosed
- 2026-10-05: patched