UBUNTU-CVE-2026-123817: Medium severity ubuntu/python-aiohttp vulnerability

Published Nov 12, 2026
·
Updated

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the WebSocket reader retains one bytes object for each transport read while reassembling an incomplete frame. A malicious peer can split a frame into many tiny reads so per-object overhead substantially exceeds the payload bytes allowed by maxmsgsize. The condition affects a server receiving frames from a malicious client and a client receiving frames from a malicious server, and can cause excessive memory consumption or denial of service. This issue is fixed in version 3.14.4.

Affected Software

7 affected components
ubuntu/python-aiohttp*
ubuntu/python-aiohttp*
ubuntu/python-aiohttp*
ubuntu/python-aiohttp*
ubuntu/python-aiohttp*
ubuntu/python-aiohttp*
ubuntu/python-aiohttp*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.4

Event History

Nov 12, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Both AIOHTTP WebSocket servers that accept connections from malicious clients and AIOHTTP WebSocket clients that connect to malicious servers are affected. The issue applies when an incomplete WebSocket frame can be delivered across many very small transport reads.

2

What must an attacker do to trigger excessive memory use?

The attacker must act as the WebSocket peer and split an incomplete frame into many tiny transport reads. AIOHTTP retains a separate bytes object for each read while reassembling the frame, allowing object overhead to exceed the payload limit imposed by max_msg_size.

3

Does max_msg_size prevent this denial of service?

No. Although max_msg_size limits payload bytes, the accumulated per-object overhead from many tiny reads can substantially exceed the allowed payload size.

4

What version contains the fix?

The issue is fixed in AIOHTTP version 3.14.4. Systems using earlier versions are affected according to the available information.

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