RHSA-2026:98106HighCVSS 7.7

Red Hat Security Advisory: python-tornado security update

Published
November 11, 2026
Last Modified
November 11, 2026

🔗 CVE IDs covered (5)

CVE-2026-49853 →CVE-2026-49855 →CVE-2026-82397 →CVE-2026-91990 →CVE-2026-103262 →

📋 Description

CVE-2026-49853 — tornado: Tornado: Information disclosure via improper handling of credentials during HTTP redirects CVE-2026-49855 — tornado: Tornado: Denial of Service via uncontrolled gzip decompression memory consumption CVE-2026-82397 — python-tornado: Tornado: Denial of Service via excessive URL-encoded body fields CVE-2026-91990 — tornado: Tornado: Denial of Service via memory amplification in multipart parsing CVE-2026-103262 — tornado: Tornado: Denial of Service via decompression bomb in CurlAsyncHTTPClient

🎯 Affected products14

  • Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python-tornado-0:6.5.10-0.el9_2.1.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python-tornado-debugsource-0:6.5.10-0.el9_2.1.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python-tornado-debugsource-0:6.5.10-0.el9_2.1.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python-tornado-debugsource-0:6.5.10-0.el9_2.1.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python-tornado-debugsource-0:6.5.10-0.el9_2.1.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python3-tornado-0:6.5.10-0.el9_2.1.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python3-tornado-0:6.5.10-0.el9_2.1.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python3-tornado-0:6.5.10-0.el9_2.1.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python3-tornado-0:6.5.10-0.el9_2.1.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python3-tornado-debuginfo-0:6.5.10-0.el9_2.1.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python3-tornado-debuginfo-0:6.5.10-0.el9_2.1.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python3-tornado-debuginfo-0:6.5.10-0.el9_2.1.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • python3-tornado-debuginfo-0:6.5.10-0.el9_2.1.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Applications utilizing Tornado's SimpleAsyncHTTPClient can mitigate this issue by explicitly disabling automatic redirection following. This can be achieved by setting `follow_redirects=False` when making HTTP requests. Manually handling redirects allows applications to ensure sensitive headers are not inadvertently sent to unintended origins. Disabling automatic redirects may alter application behavior that relies on this feature. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: Restrict request payload sizes or maximum form field counts at an upstream web application firewall (WAF) or reverse proxy layer before HTTP requests reach the Tornado application worker. Workaround: Restrict outbound HTTP client requests to trusted destinations and avoid using the CurlAsyncHTTPClient backend when fetching untrusted web content. 1. Application configuration: Configure Tornado applications to utilize the default SimpleAsyncHTTPClient instead of CurlAsyncHTTPClient, provided specialized libcurl functionality (such as custom proxy configurations or specific TLS options) is not required. The default client enforces strict size boundaries on compressed and uncompressed response bodies. 2. Network egress filtering: Implement firewall rules or egress network policies to restrict outbound HTTP/HTTPS connections exclusively to verified, trustworthy endpoints, preventing the client from contacting potentially malicious third-party servers. 3. Operational controls: Ensure that user-supplied or untrusted URLs are validated, sanitized, or rejected before initiating outbound retrieval requests. Caveats: Switching the HTTP client backend from CurlAsyncHTTPClient to SimpleAsyncHTTPClient may disrupt services that depend on libcurl-specific features. Enforcing egress filtering may block connections to unlisted external services.

🔗 References (8)