CVE-2026-69243: AIOHTTP: HTTP request smuggling via WebSocket upgrade

Published Aug 3, 2026
·
Updated

Summary

The HTTP parsers were vulnerable to a request smuggling attack relating to WebSocket upgrades.

Impact

If using the server-side component, it may be possible for an attacker to execute a request smuggling vulnerability using an edge case in the WebSocket upgrade procedure. AIOHTT is unaware of any public exploit code.

---

Patch: https://github.com/aio-libs/aiohttp/commit/6ae358f0983c3f4d6f67692b2f8e65dc8e091c98

Other sources

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.2, the HTTP parsers were vulnerable to a request smuggling attack relating to WebSocket upgrades. If using the server-side component, an attacker may be able to execute a request smuggling vulnerability using an edge case in the WebSocket upgrade procedure. A WebSocket upgrade request with a body could cause the parser to switch protocols before the complete request body was received, leaving trailing bytes to be handled as upgraded-protocol or pipelined data rather than normal HTTP body data. This issue is fixed in version 3.14.2.

— MITRE

Affected Software

5 affected componentsFixes available
pip/aiohttp<=3.14.1
3.14.2
debian/python-aiohttp<3.8.4-1+deb12u2
3.8.4-1+deb12u2
debian/python-aiohttp*
debian/python-aiohttp<3.14.3-1
3.14.3-1
debian/python-aiohttp<=3.8.4-1+deb12u1, <=3.11.16-1+deb13u1
3.8.4-1+deb12u23.14.3-1

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.2
  2. Upgrade

    Upgrade debian/python-aiohttp to a version that resolves this vulnerability.

    Fixed in 3.8.4-1+deb12u2
  3. Upgrade

    Upgrade debian/python-aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.3-1
  4. Upgrade

    Upgrade debian/python-aiohttp to a version that resolves this vulnerability.

    Fixed in 3.8.4-1+deb12u2Fixed in 3.14.3-1
  5. Upgrade

    Upgrade aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.2Patch 6ae358f0983c3f4d6f67692b2f8e65dc8e091c98

Event History

Aug 3, 2026
CVE Published
via MITRE·08:45 PM
Data Sourced
via MITRE·08:45 PM
DescriptionWeakness
Advisory Published
via GitHub·08:46 PM
Data Sourced
via GitHub·08:46 PM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·09:16 PM
DescriptionSeverityAffected Software
Data Sourced
via Red Hat·10:03 PM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-69243?

CVE-2026-69243 has a medium severity score of 6.3 based on the CVSS v4.0 metrics.

2

What impact does CVE-2026-69243 have?

CVE-2026-69243 may allow an attacker to exploit a request smuggling vulnerability when using the server-side component during the WebSocket upgrade process.

3

How do I fix CVE-2026-69243?

To fix CVE-2026-69243, ensure you update to the latest version of the aiohttp library that addresses this vulnerability.

4

Is CVE-2026-69243 exploitable remotely?

Yes, CVE-2026-69243 can be exploited remotely, as it involves HTTP requests.

5

Which software is affected by CVE-2026-69243?

CVE-2026-69243 affects the aiohttp library, commonly installed via pip.

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