chore(deps): update dependency tornado to v6.5.8 [security] - #85
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency tornado to v6.5.8 [security]#85renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Coverage Report for CI Build 33998690037Coverage remained the same at 27.981%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
renovate
Bot
force-pushed
the
renovate/pypi-tornado-vulnerability
branch
from
June 20, 2026 20:02
93c546d to
028906e
Compare
renovate
Bot
force-pushed
the
renovate/pypi-tornado-vulnerability
branch
from
September 5, 2026 23:26
028906e to
3f18f02
Compare
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.
This PR contains the following updates:
==6.5.5→==6.5.8Tornado has out-of-bounds memory access via C extension
CVE-2026-49854 / GHSA-cx3h-4qpv-8hc9
More information
Details
Summary
Tornado's optional native extension
tornado.speedupsimplementswebsocket_maskwithout validating that themaskargument is exactly four bytes long. The C function reads four bytes frommaskunconditionally, even when Python passes a shorter byte string. This can read beyond the provided buffer, exposing up to 3 bytes of uninitialized memory.The behavior is reachable from Tornado's XSRF token decoder when
xsrf_cookies=Trueand the native extension is active.Mitigations
This bug is fixed in Tornado 6.5.6. Prior to upgrading to this version, setting the environment variable TORNADO_EXTENSION=0 will disable the vulnerable code (at the expense of reducing websocket performance).
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
tornado AsyncHTTPClient accumulates decompressed chunks without size limit (gzip bomb)
CVE-2026-49855 / GHSA-mgf9-4vpg-hj56
More information
Details
Tornado's gzip decompression routines work in limited-size chunks, but have no overall limit for the total size of decompressed chunks that they will accumulate (There has always been a limit for the total compressed size). This allows a malicious server to consume effectively unlimited amounts of memory if it is accessed via SimpleAsyncHTTPClient in its default configuration.
HTTPServeris not affected in its default configuration, but it is ifdecompress_request=Trueis set.This bug is fixed in Tornado 6.5.6.
max_body_sizeis now checked both for the compressed and cumulative decompressed size of the response.Prior to upgrading, this issue can be mitigated by setting
decompress_response=Falseor usingCurlAsyncHTTPClient.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).
Tornado: Authorization header forwarded across cross-origin redirects in SimpleAsyncHTTPClient
CVE-2026-49853 / GHSA-3x9g-8vmp-wqvf
More information
Details
Summary
When SimpleAsyncHTTPClient follows a 3xx redirect, it shallow-copies the original HTTPRequest, rewrites the URL, decrements max_redirects, and removes only the Host header. It does not clear Authorization, auth_username, auth_password, or auth_mode when the redirect target changes origin.
As a result, credentials intended for one origin can be forwarded to a different origin when follow_redirects=True, which is the default.
Beginning in Tornado 6.5.6,
SimpleAsyncHTTPClientmatches the default behavior oflibcurl(and thereforeCurlAsyncHTTPClient): When a redirect changes the scheme, host, or port of the url, theAuthorizationandCookieheaders will be removed when following the redirect.Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Tornado: CurlAsyncHTTPClient leaks per-request credentials on handle reuse
GHSA-pw6j-qg29-8w7f
More information
Details
CurlAsyncHTTPClient leaks per-request credentials on handle reuse
Summary
CurlAsyncHTTPClientpools and reusespycurlhandles across requests but doesnot reset them between requests, and several per-request options are applied with
no clearing branch. As a result, sensitive state set by one request persists onto
a later request on the same client that does not set it. Two credential vectors
are demonstrated below — a client TLS certificate (
SSLCERT/SSLKEY) and proxybasic-auth credentials (
PROXYUSERPWD) — both leaking to a different,unintended host. This affects all released versions through 6.5.6.
Details
In
tornado/curl_httpclient.py, handles are created once and returned to a freelist for reuse (
_process_queuepops the handle at line 200,_finishre-appends it at line 245), and
_curl_setup_requestis never preceded bycurl.reset(). The function clears some carried-over state on the reused handle—
unsetopt(PROXYUSERPWD)in the no-proxy branch (line 394),unsetopt(USERPWD)when no auth is set (line 495), and the HTTP-method flag reset (lines 428-432) —
but other options have no equivalent clearing path and persist until a later
request sets them again.
Vector A — client TLS certificate (
SSLCERT/SSLKEY). Set-only, no clearingbranch:
A request that sets
client_certleaves the certificate on the handle; a laterrequest without
client_certpresents it during its TLS handshake.Vector B — proxy credentials (
PROXYUSERPWD).PROXYUSERPWDis set onlyinside the credentials branch and unset only in the no-proxy
elsebranch:A request that sets a new
proxy_hostwithoutproxy_usernameupdatesPROXY/PROXYPORTbut never reaches theelse, so the previous request'scredentials persist and are sent to the new proxy.
The same class also affects
INTERFACE(lines 365-366: set only whenrequest.network_interfaceis truthy, with no clearing branch), which is alower-severity instance — a later request can be bound to a network interface it
did not request. A single fix addresses all three (see Mitigation).
PoC
Both reproduce against the pinned release using public API only
(
CurlAsyncHTTPClient,HTTPRequest, and the documented per-request arguments).Vector A — client TLS certificate
The two servers listen on different ports, so request B opens a fresh TCP+TLS
connection; the certificate can only reach server 2 via the persisted handle
option, not connection or session reuse.
Output (
pip show tornado→ 6.5.6, installed in the venv):Vector B — proxy credentials
Each proxy is a separate listener capturing the raw request bytes.
Output (
YWxpY2U6c2VjcmV0QQ==decodes toalice:secretA):Impact
of a resource whose sensitive state was not cleared (CWE-672).
options on a shared
CurlAsyncHTTPClient— for Vector A, mixing per-requestclient_certrequests with non-certificate requests; for Vector B,multiplexing requests across more than one proxy with per-proxy credentials.
handshake — proving possession of the private key and disclosing the
certificate subject and chain — to a host that was never meant to receive it.
For Vector B, proxy basic-auth credentials are transmitted (base64) to a
different proxy. If the unintended host/proxy is attacker-controlled or
attacker-influenced (a user-supplied URL, webhook target, SSRF-reachable
endpoint, or a proxy chosen from user-controlled configuration), the credential
is disclosed to the attacker.
CurlAsyncHTTPClientbackendwith the patterns above are affected. The default
SimpleAsyncHTTPClientis notaffected (and does not support proxies).
Proposed CWE: CWE-200 / CWE-672. Proposed CVSS 3.1:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N(5.9, medium); attack complexity isHigh because exploitation depends on the application using differing per-request
options on a shared client and on handle scheduling.
Mitigation
A single fix closes all instances of this class: call
curl.reset()at the startof
_curl_setup_requestand then re-apply the per-request options, so no statefrom a prior request can persist on the reused handle. (Note
curl.reset()alsoclears
CAINFO, which the current code intentionally leaves untouched — see thecomment at lines 401-409 — so that default would need to be re-established after
the reset.)
Alternatively, add explicit clearing branches mirroring the existing
PROXYUSERPWD/USERPWDhandling:Until a fix is available, use a separate
CurlAsyncHTTPClientinstance perdistinct credential set (per client certificate / per proxy credential), or use
SimpleAsyncHTTPClientwhere applicable.Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Tornado: Incomplete fix for CVE-2026-35536: cookie attribute injection re-opened via the legacy case-insensitive
**kwargspath inset_cookieGHSA-wwv5-g3v4-889x
More information
Details
Summary
The CVE-2026-35536 fix added a validation loop that rejects
[\x00-\x20\x3b\x7f], but only for thehardcoded lowercase keys
name/domain/path/samesite. The still-live deprecated**kwargspathwrites attacker-supplied attribute values straight into the
Morselwith no validation, and becauseMorsel.__setitem__is case-insensitive, a capitalized kwarg (Domain=,Path=,SameSite=,Max-Age=)routes to the same reserved attribute while bypassing the loop — re-opening
;-delimited attribute injection.The patch's regression test (
SetCookieForbiddenCharHandler) only exercises the four named params, never the**kwargspath, so the gap is not regression-covered.Affected code
tornado/web.py→RequestHandler.set_cookie: the validation loop covers only the lowercase named args;the trailing
if kwargs:loop doesmorsel[k] = vwith no character validation.Steps to reproduce
GET /upper(usesDomain=kwarg) emitsSet-Cookie: c_upper=v; Domain=evil.com; Secure; SameSite=None; Path=/;GET /lower(uses lowercasedomain=) returns aCookieError.Impact
Injection of independent cookie attributes (force/drop
Secure/HttpOnly/SameSite, rebindDomain/Path)— the same impact CVE-2026-35536 closed, via the sibling path the patch missed. Conditional on the app using
a capitalized/legacy keyword.
Suggested remediation
Apply the same
[\x00-\x20\x3b\x7f]validation to every entry in the**kwargsloop (after normalizing thekey case), or remove the deprecated kwargs path; add a regression test for capitalized kwargs.
Credit
Reported as part of an incomplete-patch measurement study (responsible disclosure).
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).
tornado: multipart split() creates huge temp list before max_parts check -> memory amplification DoS (httputil.py:34)
GHSA-8423-8fgw-73vq
More information
Details
Description
Summary
parse_multipart_form_data(httputil.py:34) callsdata.split(b"--"+boundary+b"\r\n")before themax_partscheck (:35).A 600KB body with 100k parts creates a 100k-element transient list first,
then rejects transient memory amplification (each split element is a copy).
Pre-auth HTTP DoS.
Root cause
PoC
gist: https://gist.github.com/afldl/649861f25d39b53b7edbe0298e171617
poc.py+output.txt(100k parts from 600KB transient list).Fix
Count separators without materializing the list (e.g.
data.count(b"--"+boundary)first).Credit
Reported by afldl, 2026-07.
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).
Tornado: Urlencoded body parsing omits max_num_fields, so one request can stall the event loop
CVE-2026-82397 / GHSA-mpf4-983q-p7j4
More information
Details
Summary
Tornado parses
application/x-www-form-urlencodedbodies withurllib.parse.parse_qsand does not passmax_num_fields. A body made almost entirely of separators produces tens of millions of fields, and the parse happens on the event loop before the handler runs, so a single request stalls the whole server.Where it is
tornado/escape.py, at HEADe530031405e2154654dedc4c84d5656b557ea310:max_num_fieldsis the parameter CPython added for exactly this, and it is absent.The path to it is entirely server-side and pre-dispatch.
RequestHandler._executeparses the body attornado/web.py:1821, which reachesHTTPServerRequest._parse_bodyattornado/httputil.py:636, and the urlencoded branch ofparse_body_argumentscallsparse_qs_bytesattornado/httputil.py:1030.The size that reaches it is bounded only by the body cap, which defaults to the stream's
max_buffer_sizeof 104857600 attornado/iostream.py:239, applied as the request body default attornado/http1connection.py:136-140. A 100 MB body of separators is around fifty million fields.Impact
Denial of service against the whole process, not one request. Tornado is single-threaded and the parse is synchronous on the event loop, so every other connection waits. No authentication is needed if any route accepts a form post, which is the normal case.
Suggested fix
Pass a bound:
with a conservative default and a way for applications to raise it. CPython raises
ValueErrorwhen the limit is exceeded, which maps cleanly onto a 400.Lowering the default body cap for urlencoded specifically would help too, since 100 MB of form fields is not a shape any real client sends.
Why I do not think this is a duplicate
The published tornado advisories cover out-of-bounds access in the C extension, unbounded accumulation of decompressed chunks in
AsyncHTTPClient, the Authorization header surviving cross-origin redirects, credential leakage on curl handle reuse, and cookie attribute validation. The decompression one is the nearest in spirit and is on the client side; this is the server parsing a request body. The call is unchanged at HEAD.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).
Release Notes
tornadoweb/tornado (tornado)
v6.5.8Compare Source
v6.5.7Compare Source
v6.5.6Compare Source
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.