Repository navigation
chore(deps): update dependency aiohttp to v3.14.4 [security] - #2663
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Python test results0 tests - 591 0 ✅ - 586 0s ⏱️ -55s For more details on these parsing errors, see this check. Results for commit fa02e27. ± Comparison against base commit ccd3f10. ♻️ This comment has been updated with latest results. |
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 10, 2026 15:17
817f8c9 to
98c0490
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 10, 2026 15:31
98c0490 to
97f14f9
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 10, 2026 15:40
97f14f9 to
b2a4dee
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 10, 2026 15:52
b2a4dee to
4b1eedf
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
2 times, most recently
from
November 14, 2026 09:05
6de45ed to
a211abe
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 16, 2026 15:03
a211abe to
c168289
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 16, 2026 15:40
c168289 to
c6fafff
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
2 times, most recently
from
November 16, 2026 16:56
cc3b563 to
4dd4317
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
2 times, most recently
from
November 16, 2026 19:31
345954f to
95b525e
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
2 times, most recently
from
November 16, 2026 20:42
b6740ef to
91916ff
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
2 times, most recently
from
November 17, 2026 17:55
4a94b82 to
02be5fc
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
2 times, most recently
from
November 18, 2026 02:07
cfea9f9 to
620cf00
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 18, 2026 07:44
620cf00 to
28b9913
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 18, 2026 09:45
28b9913 to
48b713b
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 20, 2026 17:55
48b713b to
943a00c
Compare
renovate
Bot
force-pushed
the
renovate/pypi-aiohttp-vulnerability
branch
from
November 20, 2026 18:06
943a00c to
fa02e27
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
3.14.3→3.14.4aiohttp: Multiple instances of excessive or unbounded memory/CPU use
CVE-2026-123817 / GHSA-2g87-pp6c-29x5
More information
Details
Summary
While reassembling a WebSocket frame that arrived across many small transport reads, the reader kept one
bytesobject per read with no bound on the count. The per-object overhead is many times larger than the payload bytes, so a frame delivered a few bytes at a time could use far more memory thanmax_msg_sizeallows.Impact
An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending a frame in a large number of tiny segments.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Secure attribute not enforced for shared cookie
CVE-2026-111063 / GHSA-494j-54xm-rwp3
More information
Details
Summary
The Secure attribute was not being enforced for the shared cookie.
Impact
It may be possible to send a shared cookie marked Secure through an unencrypted request.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
aiohttp server lacks an initial request/header timeout
CVE-2026-111064 / GHSA-5wr8-gcqf-gqf3
More information
Details
Summary
The keepalive timeout was not used during the initial portion of a request.
Impact
An attacker could keep an idle connection open indefinitely before sending any data.
Workaround
Use a reverse proxy (as recommended for all production deployments) with sensible keepalive limits.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: File descriptor exhaustion in multipart requests
CVE-2026-111066 / GHSA-9xw5-w5jj-pvcg
More information
Details
Summary
An attacker can exhaust file descriptors with specially crafted multipart requests.
Impact
If a handler uses
Request.post(), it may be possible for an attacker to use an unlimited number of file descriptors, potentially resulting in resource exhaustion.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Pure-Python parser request smuggling
CVE-2026-111750 / GHSA-pqxq-w44r-73xw
More information
Details
Summary
The pure Python parser is vulnerable to an HTTP request smuggling attack.
Impact
If users are using the Python parser (
AIOHTTP_NO_EXTENSIONS, or not a standard wheel installed), then an application may be vulnerable to a request smuggling attack.Workaround
Switch to the default C parser.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Connector pool exhaustion via Max-Age overflow
CVE-2026-111065 / GHSA-6cjc-53gc-5rqm
More information
Details
Summary
An overflow in Max-Age processing can skip closing a connection.
Impact
An attacker may be able to exhaust the connection pool temporarily, until garbage collection resolves the connections.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Cookie from subdomain can remove Host-Only Scope from existing cookies
CVE-2026-111749 / GHSA-gx76-c99x-2c96
More information
Details
Summary
A subdomain can remove the Host-Only flag from an existing cookie to a parent domain.
Impact
A user accessing untrusted subdomains could see their Host-Only protections stripped from cookies. Given most usecases won't reflect these cookies to a browser, the impact is limited.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Absolute-form request targets can spoof Request.scheme
CVE-2026-111748 / GHSA-f9xw-jh8m-3mwq
More information
Details
Summary
An attacker sending an absolute-form request can spoof the scheme used.
Impact
If user code depends on the
Request.schemeattribute for anything security related, an attacker may be able to circumvent this logic, tricking the application into thinking a connection is encrypted when it is not, or vice versa.Workaround
A WAF rule to reject absolute-form requests (legitimate requests should only use this form for proxies).
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: WebSocket receive queue limits bypassed by small or compressed messages
CVE-2026-128132 / GHSA-5rmc-48h2-hvcm
More information
Details
Summary
The WebSocket reader continued parsing frames already received after the receive queue had paused the transport, and empty messages were not counted towards the queue size. With permessage-deflate, a single read of compressed frames could add many megabytes of decompressed messages to the queue.
Impact
An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending many small or compressed messages faster than the application consumes them.
Patch: aio-libs/aiohttp@0ae5074
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Concatenated compressed streams cause excessive CPU use
CVE-2026-128131 / GHSA-h4cc-hm5h-fmm9
More information
Details
Summary
When decompressing a payload made up of many concatenated compressed members (gzip, deflate or zstd), each member was decoded by passing the entire remaining input to a new decompressor, resulting in quadratic CPU time. Empty members produce no output, so
client_max_sizeand output backpressure did not limit the work.Impact
An attacker could block the event loop of a server with a specially crafted compressed request body or WebSocket message. A malicious server could do the same to a client.
Patch: aio-libs/aiohttp@d925a80
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Pure-Python parser request replay and buffer growth behind a declined upgrade
CVE-2026-128130 / GHSA-28qf-cpwq-vmc2
More information
Details
Summary
When the pipelined request queue was full, the pure-Python parser stored the unparsed remainder internally and also returned it to the caller. After a handler declined an upgrade request, the buffered data was re-fed, so the buffer grew with each handled request and already-handled requests were dispatched to the application again.
Impact
If users are using the Python parser (
AIOHTTP_NO_EXTENSIONS, or not a standard wheel installed), an attacker could cause excessive memory use and cause pipelined requests to be processed more than once.Workaround
Switch to the default C parser.
Patch: aio-libs/aiohttp@47babd8
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Unbounded buffering of data received during an upgrade request
CVE-2026-128129 / GHSA-pw86-h8fm-j323
More information
Details
Summary
While a request flagged as an upgrade (e.g. a WebSocket handshake) was being handled, all further data received on the connection was buffered with no size limit or flow control until the handler completed.
Impact
An attacker could cause unbounded memory use by streaming data behind an upgrade request to any handler that does not immediately accept or reject the upgrade.
Patch: aio-libs/aiohttp@3d850ee
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: WebSocket max_msg_size bypass via integer overflow
CVE-2026-128128 / GHSA-3rp8-rxj8-mvjw
More information
Details
Summary
The
max_msg_sizecheck in the WebSocket reader added the declared frame length to the size of the partial message already buffered. In the C extension this addition is 64-bit arithmetic, so a declared length close to 2**63 overflowed and the check passed.Impact
An attacker could bypass
max_msg_sizeand cause unbounded memory use by streaming an oversized WebSocket message after a small non-final fragment.Workaround
If unable to upgrade, the Python reader is unaffected and can be used with
AIOHTTP_NO_EXTENSIONS=1.Patch: aio-libs/aiohttp@8cfbe9a
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Base64 multipart parts bypass client_max_size
CVE-2026-128127 / GHSA-24c4-3p7v-29cm
More information
Details
Summary
When reading a multipart part with
Content-Transfer-Encoding: base64,BodyPartReader.read_chunk()kept reading until the chunk length was a multiple of 4, with no byte limit. A part with a shortContent-Length, or a long run of whitespace, could cause the entire remaining body to be read into memory within a single call before any size check, or spin on the event loop.Impact
An attacker could bypass
client_max_sizeto cause excessive memory use, or block the event loop, with a specially crafted multipart request to any handler that reads multipart data.Patch: aio-libs/aiohttp@a555ab6
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Too many URL-encoded form fields block the event loop
CVE-2026-128126 / GHSA-xgw8-8ccx-rmqh
More information
Details
Summary
Request.post()had no limit on the number of fields in a URL-encoded form body. Inserting a large number of repeated keys into aMultiDicttook quadratic time on the event loop.Impact
An attacker could block the event loop with a form POST within the default
client_max_sizeto any handler that callsRequest.post().Patch: aio-libs/aiohttp@615fec3
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Unbounded cookie storage in client CookieJar
CVE-2026-128125 / GHSA-5pv8-vvhc-h7jv
More information
Details
Summary
Set-Cookieparsing created additional cookies from unrecognisedname=valueattributes, andCookieJarhad no limit on the number of cookies stored or sent. A server could make the client store a very large number of cookies and generate very largeCookieheaders.Impact
A malicious server could cause excessive memory and CPU use in a client, repeated on every redirect, and cause later requests to the same domain to build an excessively large
Cookieheader.Patch: aio-libs/aiohttp@6963ee0
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AIOHTTP: Event loop stall in add_domain() wildcard matching
CVE-2026-128124 / GHSA-jm3w-gw2p-xjfj
More information
Details
Summary
Application.add_domain()compiled each*in a host mask to[^:]*. With two or more wildcards in a mask, matching a longHostheader that does not match the mask took polynomial time on the event loop.Impact
An attacker could stall a server that registers a domain mask with more than one wildcard by sending requests with a long
Hostheader.Workaround
Use at most one
*in a domain mask.Patch: aio-libs/aiohttp@c6ac0e4
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aio-libs/aiohttp (aiohttp)
v3.14.4Compare Source
===================
Features
Added :class:
aiohttp.UploadTrackerfor observing a client request's upload progress -- by :user:Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13579.Switched
application/x-www-form-urlencodedparsing in:meth:
~aiohttp.web.BaseRequest.postto the faster :func:yarl.query_to_pairsparser and added the
client_max_fieldsargument to:class:
~aiohttp.web.Application(default1000) to cap the number of formfields accepted by :meth:
~aiohttp.web.BaseRequest.post. Forms with morethan 1000 fields now receive a
413response unless the cap is raised;0disables it -- by :user:bdraco.Related issues and pull requests on GitHub:
:issue:
13738.Added constants to
aiohttp.hdrsfor widely used headers: those thatbrowsers send on every request (
Sec-Fetch-*,Sec-CH-UA*,Sec-GPC,Upgrade-Insecure-Requests,Priority), W3C trace context(
traceparent,tracestate,baggage), response security, reportingand caching headers, the remaining RFC 9110 and RFC 9530 fields,
Content-IDand common de facto proxy and application headers, andgrouped the constants by where the header is defined. The C parser returns
these names as the shared :class:
~multidict.istrconstants instead of new:class:
strobjects, which made parsing a typical browser request about9% cheaper -- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
13886.Bug fixes
Remove overlapping slots in
RequestHandler,fix broken slots inheritance in :py:class:
~aiohttp.web.StreamResponse.Related issues and pull requests on GitHub:
:issue:
6547.Fixed a segmentation fault in the C HTTP parser on Python 3.12 and newer when payload decompression raised an error while pending decompressed data was being drained, as seen with
brotlicffi1.2 -- by :user:bdraco.Related issues and pull requests on GitHub:
:issue:
13203, :issue:13249.Rejected control characters in the request target in the pure-Python HTTP parser,
matching the llhttp-backed parser, which already refuses them
-- by :user:
arshsmith1.Related issues and pull requests on GitHub:
:issue:
13212.Stripped the trailing whitespace from header values in the C HTTP parser,
so that it matches the pure-Python parser and :rfc:
9110#section-5.5-- by :user:
LuShadowX.Related issues and pull requests on GitHub:
:issue:
13246.Fixed the WebSocket reader rejecting a compressed data frame with close code 1002 when a control frame arrived before the first data frame (regression in 3.14.2) -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13274.Fixed internally retried requests sending a truncated body when the request
data was a file object.
Related issues and pull requests on GitHub:
:issue:
13329, :issue:13330.Fixed event loop state possibly being corrupted on Python 3.12+ -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13346.Fixed the HTTP parser raising :exc:
~aiohttp.ClientPayloadErrorwhen a fully receivedContent-Lengthbody was pending completion -- by :user:Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13348.Bounded the per-read object overhead the WebSocket reader retains while reassembling a frame delivered across many small reads; the reads are joined once when the frame completes, and folded into a single buffer if they exceed a fragment cap, so a frame dribbled in tiny reads cannot pin unbounded per-read overhead -- by :user:
Dreamsorcererand :user:bdraco.Related issues and pull requests on GitHub:
:issue:
13352, :issue:13488.Fixed requests pipelined behind a request whose upgrade the handler declined
going unanswered once there were more of them than the per-connection queue
holds. With the pure-Python parser the same requests were also served more
than once -- by :user:
rodrigobnogueira.Related issues and pull requests on GitHub:
:issue:
13356.Reduced CPU consumption when encountering many concatenated members in a compressed payload and rejected large amounts of members -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13362.Fixed excessive memory consumption with small WebSocket messages -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13393.Fixed an integer overflow on too large messages -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13415.Switched multipart handling to use spooled temporary files to reduce number of file descriptors needed -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13426.Fixed a limit on message tail after an upgrade request -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13501.Fixed some edge case handling in multipart parts using base 64 encoding -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13509.Fixed Cython 3.3.0 failing to compile the WebSocket reader: dropped the
Final[...]annotation fromALLOWED_CLOSE_CODESand theintannotation from the local
start_posinWebSocketReader._feed_data,both of which conflicted with declarations in
reader_c.pxdunderCython 3.3.0 -- by :user:
Georgefifth.Related issues and pull requests on GitHub:
:issue:
13520.Fixed the WebSocket reader accepting a new data frame injected between the
fragments of an in-progress message; per :rfc:
6455#section-5.4every frameafter the first fragment and before the
FINmust be a continuation, andsuch a stream is now rejected as a protocol error -- by :user:
arshsmith1.Related issues and pull requests on GitHub:
:issue:
13553.Fixed a connection being eligible for reuse after its request was cancelled
or failed while waiting for a
100 Continueresponse or finalizing thebody; the request headers were already sent, so reusing the connection
corrupted the next request on it -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13579.Fixed
BaseRequest.http_rangenot accepting case-insensitive range units -- by :user:Manny7717.Related issues and pull requests on GitHub:
:issue:
13580, :issue:13581.Fixed
CookieJar.update_cookies()to copy user-passed mutableMorselobjects -- by :user:Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13637.Fixed unbounded memory growth on a client WebSocket connection. A frame
protocol error detaches the reader but leaves the connection upgraded, so a
peer could stream unlimited data into an internal buffer when the application
never called :meth:
~aiohttp.ClientWebSocketResponse.receive; that data isnow discarded, since nothing can parse it. Data arriving before the reader is
installed is bounded by
read_bufsize, which now applies to this buffer aswell as to :attr:
~aiohttp.ClientResponse.content-- by :user:
bdraco.Related issues and pull requests on GitHub:
:issue:
13655, :issue:13743.Fixed pure-Python request parser not reading a body in a
HEADrequest -- by :user:Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13671.Fixed host-only cookie state being lost on expiration -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13674.Fixed a possible
OverflowErroron cookies and a connection not being closed properly -- by :user:Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13677.The first-request deadline now also closes connections whose first request body stalls, while a body that is still arriving extends the deadline instead of being interrupted -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13681.Fixed idle connections not being closed if no request was received -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13681.Fixed :meth:
~aiohttp.web.Application.add_domainnot routing a request toits domain application when the
Hostheader carried a port and thedomain was registered without one, or, for a wildcard domain, uppercase
letters -- by :user:
rodrigobnogueira.Related issues and pull requests on GitHub:
:issue:
13693.Added empty
__slots__toAbstractRouteDefso thatRouteDefandStaticDefinstances no longer carry an unused__dict__.Related issues and pull requests on GitHub:
:issue:
13716.Fixed
BaseConnector(keepalive_timeout=None)crashing on the second request to the same host withTypeError: '<=' not supported between instances of 'float' and 'NoneType'-- by :user:ishan-1010.Related issues and pull requests on GitHub:
:issue:
13756, :issue:13757.Fixed a crash in :meth:
~aiohttp.BodyPartReader.read_chunkon a body partwith an explicit
Content-Length: 0: the part fell through to thestreaming read strategy, whose minimum chunk size assertion then failed for
chunk sizes below the boundary length. Such parts now yield an immediate
empty chunk, like any other part with a known length
-- by :user:
istoolsfox.Related issues and pull requests on GitHub:
:issue:
13758, :issue:13760.Fixed
Set-Cookieparsing treating unrecognized attributes as additionalcookies. Each
Set-Cookieheader now sets exactly one cookie andunrecognized attributes are ignored, per :rfc:
6265#section-5.2, preventinga malicious server from creating an attacker-selected number of cookie
objects (and correspondingly large outgoing
Cookieheaders) from abounded amount of response data.
DummyCookieJar, andCookieJarinsafe mode for IP-address origins, no longer parse
Set-Cookieheaders atall -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13800.Fixed the web server trusting the scheme of an absolute-form request-target -- by :user:
Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13821.Fixed
CookieJar.filter_cookies()sending shared cookies (cookies without aDomainattribute) markedSecureover unencrypted connections -- by :user:Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13830.Fixed per-request cookies (the
cookiesargument of a request method) markedSecurenot being sent to origins listed inCookieJar'streat_as_secure_origin-- by :user:Dreamsorcerer.Related issues and pull requests on GitHub:
:issue:
13833.Fixed the connection to an HTTP proxy staying open until garbage collection, and being reported as
Unclosed connection, when sending theCONNECTrequest for an HTTPS tunnel failed -- by :user:Garbsener.Related issues and pull requests on GitHub:
:issue:
13841.Resolved a redirect
Locationwith the scheme of the current URL butwithout
//, such ashttp:/pathorhttp:path, against thecurrent URL, as browsers do, instead of treating it as an absolute URL
without a host
-- by :user:
asvetlov.Related issues and pull requests on GitHub:
:issue:
13855.Rejected absolute-form request targets without
//or with an emptyhost, such as
http:/example.com/orhttp:///example.com/, beforeparsing them with yarl, which reads a host from them in its WHATWG mode;
RFC 9110 requires a host for `
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.