Quick answers
- Is CVE-2026-69243 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69243 being exploited in the wild.
- How severe is CVE-2026-69243?
- Medium severity, with a CVSS score of 4, published 3 August 2026.
- Which products and versions are affected?
- aiohttp (PyPI) <= 3.14.1, ECOSYSTEM:introduced=0,fixed=3.14.2.
- Is there a fix for CVE-2026-69243?
- Yes. aiohttp (PyPI): upgrade to 3.14.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-69243 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-69243?
- Check whether you run 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.2 or later
pip install "aiohttp>=3.14.2"
Technical details
AIOHTTP's server-side component contains a flaw in its HTTP parser related to the WebSocket upgrade procedure (CWE-444). An attacker can exploit an edge case during the handshake to smuggle a second HTTP request within what appears to be a single connection. This is a network-based attack with high complexity, as it requires specific timing or formatting to bypass the parser's logic. Successful exploitation could allow an attacker to bypass security proxies or perform unauthorized actions on the backend server. The issue is fixed in version 3.14.2.
Affected products
- aio-libs aiohttp <= 3.14.1
Identifiers
- CVE-2026-69243
- GHSA-mfx4-hv73-q22v
- PYSEC-2026-3546
Timeline
- 2026-07-26: disclosed
- 2026-08-03: advisory
- 2026-08-03: patched: Version 3.14.2 released