How many CVEs have patched _handle_force_timeout?

3 published CVEs changed _handle_force_timeout in tornadoweb/tornado, in 2 distinct patches totalling 39 changed lines, between 2026 and 2026.

What is the latest CVE that changed _handle_force_timeout?

CVE-2026-49855 (tornado AsyncHTTPClient accumulates decompressed chunks without size limit (gzip bomb)), published 2026-07-14, changed lines 181 of tornado/curl_httpclient.py.

How does _handle_force_timeout compare to the rest of tornadoweb/tornado?

tornadoweb/tornado has 16 CVEs with a located fix in total; 3 of them changed _handle_force_timeout.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

tornadoweb/tornado

Function

_handle_force_timeout

Name: _handle_force_timeout in tornadoweb/tornado: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

tornado/curl_httpclient.py

Last patched July 14, 2026

3

CVEs

That changed this function

2

Distinct patches

Backports counted once

39

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_handle_force_timeout in tornadoweb/tornado was changed by 3 published CVE fixes in 2026, in 2 distinct patches that added or removed 39 lines in total.

tornadoweb/tornado has 16 CVEs with a located fix in total, so 19% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _handle_force_timeout, newest first, with the lines each fix touched.

tornado AsyncHTTPClient accumulates decompressed chunks without size limit (gzip bomb)
CVE-2026-49855 · line 181 · +0 −13
High · CVSS 7.5
EPSS 0.6%2026-07-14
Tornado: Out-of-bounds memory access in C extension
CVE-2026-49854 · line 181 · +0 −13
Medium · CVSS 5.3
EPSS 0.4%2026-07-14
Tornado: Authorization header forwarded across cross-origin redirects in SimpleAsyncHTTPClient
CVE-2026-49853 · line 181 · +0 −13
High · CVSS 7.7
EPSS 0.5%2026-07-14

Get an alert when the next CVE fix lands in tornadoweb/tornado, with the patched functions.

Monitor tornado CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in tornadoweb/tornado changed by the most CVE fixes.

_websocket_mask_python4 CVEs · tornado/util.py parse_body_arguments3 CVEs · tornado/httputil.py parse_multipart_form_data3 CVEs · tornado/httputil.py close3 CVEs · tornado/curl_httpclient.py initialize3 CVEs · tornado/curl_httpclient.py ioctl3 CVEs · tornado/curl_httpclient.py

All patched functions in tornadoweb/tornado

Frequently asked questions

Common questions about CVE fixes to _handle_force_timeout.

How many CVEs have patched _handle_force_timeout?: 3 published CVEs changed _handle_force_timeout in tornadoweb/tornado, in 2 distinct patches totalling 39 changed lines, between 2026 and 2026.
What is the latest CVE that changed _handle_force_timeout?: CVE-2026-49855 (tornado AsyncHTTPClient accumulates decompressed chunks without size limit (gzip bomb)), published 2026-07-14, changed lines 181 of tornado/curl_httpclient.py.
How does _handle_force_timeout compare to the rest of tornadoweb/tornado?: tornadoweb/tornado has 16 CVEs with a located fix in total; 3 of them changed _handle_force_timeout.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track tornadoweb/tornado CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing