Source: python-aiohttp
Version: 3.14.3-1
X-Debbugs-CC: [email protected]
Severity: grave
Tags: security upstream

Hi,

The following vulnerabilities were published for python-aiohttp.

CVE-2026-128124[0]:
| AIOHTTP is an asynchronous HTTP client/server framework for asyncio
| and Python. Prior to 3.14.4, Application.add_domain() converts every
| asterisk wildcard in a domain mask into a greedy regular-expression
| fragment, so a mask containing two or more wildcards can take
| polynomial time to reject a long Host header that does not match. A
| remote attacker can repeatedly send such headers to a server
| configured with a multi-wildcard domain mask and stall the event
| loop. This issue is fixed in version 3.14.4.


CVE-2026-128125[1]:
| AIOHTTP is an asynchronous HTTP client/server framework for asyncio
| and Python. Prior to 3.14.4, Set-Cookie parsing treats unrecognized
| name=value attributes as additional cookies, while CookieJar does
| not limit the number of cookies stored or sent. A malicious server
| can make an aiohttp client accumulate a very large cookie set,
| consume memory and CPU repeatedly across redirects, and construct an
| excessively large Cookie header for later requests to the same
| domain. This issue is fixed in version 3.14.4.


CVE-2026-128126[2]:
| AIOHTTP is an asynchronous HTTP client/server framework for asyncio
| and Python. Prior to 3.14.4, Request.post() does not limit the
| number of fields in a URL-encoded form body, and inserting many
| repeated keys into MultiDict takes quadratic time on the event loop.
| A remote attacker can send a form POST within client_max_size to a
| handler that calls Request.post() and block the event loop. This
| issue is fixed in version 3.14.4.


CVE-2026-128127[3]:
| AIOHTTP is an asynchronous HTTP client/server framework for asyncio
| and Python. Prior to 3.14.4, BodyPartReader.read_chunk() processing
| a multipart part with Content-Transfer-Encoding set to base64 keeps
| reading until the chunk length is a multiple of four without
| enforcing a byte limit. A short Content-Length or a long run of
| whitespace can cause one call to read the remaining body into memory
| before the size check or spin on the event loop. A remote attacker
| can send such a multipart request to a handler that reads multipart
| data and bypass client_max_size. This issue is fixed in version
| 3.14.4.


CVE-2026-128128[4]:
| AIOHTTP is an asynchronous HTTP client/server framework for asyncio
| and Python. Prior to 3.14.4, the C WebSocket reader adds a declared
| frame length to the size of an already buffered partial message
| using signed 64-bit arithmetic. A length near two to the power of 63
| can overflow, allowing the max_msg_size check to pass. A remote peer
| can send a small non-final fragment followed by an oversized message
| and cause unbounded memory consumption. The Python WebSocket reader
| is unaffected. This issue is fixed in version 3.14.4.


CVE-2026-128129[5]:
| AIOHTTP is an asynchronous HTTP client/server framework for asyncio
| and Python. Prior to 3.14.4, aiohttp buffers all additional
| connection data received while a request marked for upgrade, such as
| a WebSocket handshake, is being handled, without a size limit or
| flow control. A remote attacker can stream data behind an upgrade
| request to a handler that does not immediately accept or reject the
| upgrade and cause unbounded memory consumption. This issue is fixed
| in version 3.14.4.


CVE-2026-128130[6]:
| AIOHTTP is an asynchronous HTTP client/server framework for asyncio
| and Python. Prior to 3.14.4, when the pipelined request queue is
| full, the pure-Python parser stores the unparsed remainder
| internally and also returns the same data to its caller. After a
| handler declines an upgrade request, the caller feeds the remainder
| back to the parser, causing the buffer to grow with each handled
| request and dispatching already-handled requests to the application
| again. The issue affects deployments using AIOHTTP_NO_EXTENSIONS or
| otherwise running without the standard C-extension wheel, and can
| cause excessive memory use and repeated request processing. This
| issue is fixed in version 3.14.4.


CVE-2026-128131[7]:
| AIOHTTP is an asynchronous HTTP client/server framework for asyncio
| and Python. Prior to 3.14.4, aiohttp decompresses each member of a
| payload containing many concatenated gzip, deflate, or zstd streams
| by passing the entire remaining input to a new decompressor, causing
| quadratic CPU use. Empty members produce no output, so
| client_max_size and output backpressure do not limit the work. A
| remote attacker can block a server event loop with a crafted
| compressed request body or WebSocket message, and a malicious server
| can similarly block a client. This issue is fixed in version 3.14.4.


CVE-2026-128132[8]:
| AIOHTTP is an asynchronous HTTP client/server framework for asyncio
| and Python. Prior to 3.14.4, the WebSocket reader continues parsing
| frames already received after the receive queue pauses the
| transport, and empty messages are not counted toward the queue size.
| With permessage-deflate, one read of compressed frames can add many
| megabytes of decompressed messages to the receive queue. A remote
| peer can send many small or compressed messages faster than the
| application consumes them and cause excessive memory use in a server
| or client. This issue is fixed in version 3.14.4.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-128124
    https://www.cve.org/CVERecord?id=CVE-2026-128124
[1] https://security-tracker.debian.org/tracker/CVE-2026-128125
    https://www.cve.org/CVERecord?id=CVE-2026-128125
[2] https://security-tracker.debian.org/tracker/CVE-2026-128126
    https://www.cve.org/CVERecord?id=CVE-2026-128126
[3] https://security-tracker.debian.org/tracker/CVE-2026-128127
    https://www.cve.org/CVERecord?id=CVE-2026-128127
[4] https://security-tracker.debian.org/tracker/CVE-2026-128128
    https://www.cve.org/CVERecord?id=CVE-2026-128128
[5] https://security-tracker.debian.org/tracker/CVE-2026-128129
    https://www.cve.org/CVERecord?id=CVE-2026-128129
[6] https://security-tracker.debian.org/tracker/CVE-2026-128130
    https://www.cve.org/CVERecord?id=CVE-2026-128130
[7] https://security-tracker.debian.org/tracker/CVE-2026-128131
    https://www.cve.org/CVERecord?id=CVE-2026-128131
[8] https://security-tracker.debian.org/tracker/CVE-2026-128132
    https://www.cve.org/CVERecord?id=CVE-2026-128132

Regards,
Salvatore

Reply via email to