Summary
This update for python-aiohttp fixes the following issues
- CVE-2026-22815: insufficient restrictions in header/trailer handling can cause uncapped memory usage and a denial of
service (bsc#1261320).
- CVE-2026-34513: unbounded DNS cache can cause a excessive memory usage and lead to a denial of service (bsc#1261321).
- CVE-2026-34514: `content_type` parameter manipulation can lead to header injection (bsc#1261322).
- CVE-2026-34516: response with excessive multipart headers can use more memory than intended and cause a denial of
service (bsc#1261329).
- CVE-2026-34517: large multipart form fields read into memory without size check can cause a denial of service
(bsc#1261331).
- CVE-2026-34518: retained `Cookie` and `Proxy-Authorization` headers when following redirects can lead to information
disclosure (bsc#1261332).
- CVE-2026-34519: response `reason` parameter can be use to perform header injection (bsc#1261334).
- CVE-2026-34520: improper character handling by C parser can lead to header injection (bsc#1261335).
- CVE-2026-34525: multiple `Host` headers allow for potential security bypass in proxy servers (bsc#1261343).
- CVE-2026-34993: loading untrusted input in `CookieJar.load()` can lead to arbitrary code execution (bsc#1267471).
- CVE-2026-47265: cookies set with the `cookies` parameter on requests are sent after following a cross-origin redirect
and can leak sensitive data (bsc#1267561).
- CVE-2026-50269: improper validation of user-controlled strings allows for CRLF injection in multipart headers
(bsc#1268398).
- CVE-2026-54273: no limit in the HTTP/1 pipelined request queue can lead to excessive resource consumption
(bsc#1268543).
- CVE-2026-54274: incomplete websocket frame payloads can bypass memory use limits and cause a DoS via excessive
resource consumption (bsc#1268544).
- CVE-2026-54275: `server_hostname` TLS SNI check bypass when an existing connection is reused (bsc#1268549).
- CVE-2026-54277: `max_line_size` bypass when using the optimised C HTTP parser can lead to excessive resource
consumption (bsc#1268556).
- CVE-2026-54278: unread compressed request bodies can bypass `client_max_size` during cleanup and cause a DoS
(bsc#1268559).
- CVE-2026-54279: host-only cookies become domain cookies after `CookieJar` persistence (bsc#1268560).
- CVE-2026-54280: payload resources are not closed correctly when a client disconnects in the middle of a write and
can cause resource starvation (bsc#1268561).
Fixed packages 12
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLE HPC 15 SP4 Linux Enterprise High Performance Computing 15 SP4-ESPOS | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLE HPC 15 SP4 Linux Enterprise High Performance Computing 15 SP4-LTSS | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLE HPC 15 SP5 Linux Enterprise High Performance Computing 15 SP5-ESPOS | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLE HPC 15 SP5 Linux Enterprise High Performance Computing 15 SP5-LTSS | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLES 15 SP4 Linux Enterprise Module for Public Cloud 15 SP4 | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLES 3 Linux Enterprise Module for Python 3 15 SP7 | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLES 15 SP4 Linux Enterprise Server 15 SP4-LTSS | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLES 15 SP5 Linux Enterprise Server 15 SP5-LTSS | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLES 15 SP6 Linux Enterprise Server 15 SP6-LTSS | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLES for SAP 15 SP4 Linux Enterprise Server for SAP Applications 15 SP4 | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLES for SAP 15 SP5 Linux Enterprise Server for SAP Applications 15 SP5 | python-aiohttp | 3.9.3-150400.10.43.1 |
| SUSE · SLES for SAP 15 SP6 Linux Enterprise Server for SAP Applications 15 SP6 | python-aiohttp | 3.9.3-150400.10.43.1 |
Vulnerabilities 19
-
Medium 6.9
AIOHTTP: Uncapped memory usage possible through aiohttp allowing unlimited trailer headers
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, insufficient restrictions in header/trailer handling could cause uncapped memory usage. This issue has been patched in version 3.13.4.
-
Medium 6.6
AIOHTTP: Multipart Header Size Bypass
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, a response with an excessive number of multipart headers may be allowed to use more memory than intended, potentially allowing a DoS vulnerability. This i…
-
Medium 6.6
AIOHTTP vulnerable to cross-origin redirect with per-request cookies
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.14.0, cookies set with the `cookies` parameter on requests are sent after following a cross-origin redirect. If a developer uses the `cookies` parameter on a pe…
-
Medium 6.6
AIOHTTP: HTTP/1 Pipelined Requests Queue Without Limit
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, no limit was present on the number of pipelined requests that could be queued. An attacker may be able to use pipelined requests to use excessive amounts of memor…
-
Medium 6.6
AIOHTTP: Incomplete websocket frame payloads bypass memory limits
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, if an attacker sends large incomplete websocket frame payloads, it may be possible to bypass the usual size limits on memory use. This vulnerability is fixed in 3…
-
Medium 6.6
AIOHTTP: C HTTP Parser Bypasses max_line_size for Fragmented Lines
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, it is possible to bypass the max_line_size check in parts of an HTTP request in the C parser. If using the optimised C parser (the default in pre-built wheels), t…
-
Medium 6.6
AIOHTTP: Unread Compressed Request Bodies Bypass client_max_size During Cleanup
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, during cleanup it is possible for a compressed request body to be decompressed into memory in one chunk. An attacker may be able to send a compressed payload in s…
-
Medium 6.4
AIOHTTP Vulnerable to Deserialization of Untrusted Data
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.14.0, using ``CookieJar.load()`` with untrusted input may allow arbitrary code execution. Most applications using this function will be doing so with the user's…
-
Medium 6.3
AIOHTTP: Duplicate Host header accepted
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, multiple Host headers were allowed in aiohttp. This issue has been patched in version 3.13.4.
-
Low 2.7
AIOHTTP: Denial of Service (DoS) via Unbounded DNS Cache in TCPConnector
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, an unbounded DNS cache could result in excessive memory usage possibly resulting in a DoS situation. This issue has been patched in version 3.13.4.
-
Low 2.7
AIOHTTP: CRLF injection in multipart part content type header construction
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, an attacker who controls the content_type parameter in aiohttp could use this to inject extra headers or similar exploits. This issue has been patched in …
-
Low 2.7
AIOHTTP: Late size enforcement for non-file multipart fields causes memory DoS
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, for some multipart form fields, aiohttp read the entire field into memory before checking client_max_size. This issue has been patched in version 3.13.4.
-
Low 2.7
AIOHTTP: Cookie and Proxy-Authorization headers leaked on cross-origin redirect
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, when following redirects to a different origin, aiohttp drops the Authorization header, but retains the Cookie and Proxy-Authorization headers. This issue…
-
Low 2.7
AIOHTTP: HTTP response splitting via \r in reason phrase
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, an attacker who controls the reason parameter when creating a Response may be able to inject extra headers or similar exploits. This issue has been patche…
-
Low 2.7
AIOHTTP: C parser (llhttp) accepts null bytes and control characters in response header values - header injection / security bypass
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, the C parser (the default for most installs) accepted null bytes and control characters in response headers. This issue has been patched in version 3.13.4.
-
Low 2.7
AIOHTTP: CRLF injection in multipart headers
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.0, attacker-controlled input included into multipart/payload headers can be used to modify a request to inject additional headers or similar. In the unlikely situati…
-
Low 2.7
AIOHTTP: TLS Server Hostname Override Is Ignored When Reusing HTTPS Connections
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed when an existing connection is reused. If an application makes multiple requests to the same domain, but with di…
-
Low 1.7
AIOHTTP: Payload Response Resources Are Not Closed After Mid-Body Disconnect
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, payload resources are not closed correctly when a client disconnects in the middle of a write. If a payload is using an open file or similar limited resource, the…
-
Low 1.3
AIOHTTP: Host-Only Cookies Become Domain Cookies After CookieJar Persistence
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, host-only cookies that are saved with CookieJar.save() and then restored later with CookieJar.load() lose their host-only status. This vulnerability is fixed in 3…
References
-
report
https://bugzilla.suse.com/1261320
-
report
https://bugzilla.suse.com/1261321
-
report
https://bugzilla.suse.com/1261322
-
report
https://bugzilla.suse.com/1261329
-
report
https://bugzilla.suse.com/1261331
-
report
https://bugzilla.suse.com/1261332
-
report
https://bugzilla.suse.com/1261334
-
report
https://bugzilla.suse.com/1261335
-
report
https://bugzilla.suse.com/1261343
-
report
https://bugzilla.suse.com/1267471
-
report
https://bugzilla.suse.com/1267561
-
report
https://bugzilla.suse.com/1268398
-
report
https://bugzilla.suse.com/1268543
-
report
https://bugzilla.suse.com/1268544
-
report
https://bugzilla.suse.com/1268549
-
report
https://bugzilla.suse.com/1268556
-
report
https://bugzilla.suse.com/1268559
-
report
https://bugzilla.suse.com/1268560
-
report
https://bugzilla.suse.com/1268561
-
web
https://www.suse.com/security/cve/CVE-2026-22815
-
web
https://www.suse.com/security/cve/CVE-2026-34513
-
web
https://www.suse.com/security/cve/CVE-2026-34514
-
web
https://www.suse.com/security/cve/CVE-2026-34516
-
web
https://www.suse.com/security/cve/CVE-2026-34517
-
web
https://www.suse.com/security/cve/CVE-2026-34518
-
web
https://www.suse.com/security/cve/CVE-2026-34519
-
web
https://www.suse.com/security/cve/CVE-2026-34520
-
web
https://www.suse.com/security/cve/CVE-2026-34525
-
web
https://www.suse.com/security/cve/CVE-2026-34993
-
web
https://www.suse.com/security/cve/CVE-2026-47265
-
web
https://www.suse.com/security/cve/CVE-2026-50269
-
web
https://www.suse.com/security/cve/CVE-2026-54273
-
web
https://www.suse.com/security/cve/CVE-2026-54274
-
web
https://www.suse.com/security/cve/CVE-2026-54275
-
web
https://www.suse.com/security/cve/CVE-2026-54277
-
web
https://www.suse.com/security/cve/CVE-2026-54278
-
web
https://www.suse.com/security/cve/CVE-2026-54279
-
web
https://www.suse.com/security/cve/CVE-2026-54280