Is tornado 4.0 vulnerable?
PyPI · 3 releases from 4.0.0 to 4.0.2 · latest tornado is 6.6.1 · checked 18 Nov 2026
Yes: 25 known advisories
Yes. tornado 4.0.2, the last 4.0 release, is affected by 25 known security advisories (11 high, 11 medium, 3 low), including CVE-2026-103262, CVE-2026-103263, CVE-2026-82397. Upgrade to 6.6.1 or later to fix all of them.
pip install 'tornado>=6.6.1'Is your project on an affected tornado?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting tornado 4.0.2
Tornado: Open redirect via triple-slash redirect paths
- Affected
- <6.6.1
- Fixed in
- 6.6.1
Tornado: Event loop blocking and excess memory use from chunked bodies with many small chunks
- Affected
- <6.6
- Fixed in
- 6.6
Tornado: Open redirect in RedirectHandler via protocol-relative URLs
- Affected
- <6.6
- Fixed in
- 6.6
Tornado: Quadratic CPU usage when parsing HTTP headers with line folding
- Affected
- <6.6
- Fixed in
- 6.6
Tornado: Unbounded query-string argument count allows event-loop-stalling DoS
- Affected
- <6.5.9
- Fixed in
- 6.5.9
tornado: CurlAsyncHTTPClient enforces no response-size limit — decompression bomb drives unbounded memory accumulation to OOM
- Affected
- <6.5.9
- Fixed in
- 6.5.9
Tornado: StaticFileHandler follows symlinks outside static root (path traversal)
- Affected
- <6.5.9
- Fixed in
- 6.5.9
Tornado: Urlencoded body parsing omits max_num_fields, so one request can stall the event loop
- Affected
- <6.5.8
- Fixed in
- 6.5.8
tornado: multipart split() creates huge temp list before max_parts check -> memory amplification DoS (httputil.py:34)
- Affected
- <6.5.8
- Fixed in
- 6.5.8
Tornado: Quadratic DoS via Crafted Multipart Parameters
- Affected
- <6.5.3
- Fixed in
- 6.5.3
Tornado: Quadratic DoS via Repeated Header Coalescing
- Affected
- <6.5.3
- Fixed in
- 6.5.3
Tornado vulnerable to Header Injection and XSS via reason argument
- Affected
- <6.5.3
- Fixed in
- 6.5.3
Tornado: CurlAsyncHTTPClient leaks per-request credentials on handle reuse
- Affected
- <6.5.7
- Fixed in
- 6.5.7
Tornado: Authorization header forwarded across cross-origin redirects in SimpleAsyncHTTPClient
- Affected
- <6.5.6
- Fixed in
- 6.5.6
tornado AsyncHTTPClient accumulates decompressed chunks without size limit (gzip bomb)
- Affected
- <6.5.6
- Fixed in
- 6.5.6
Tornado has out-of-bounds memory access via C extension
- Affected
- <6.5.6
- Fixed in
- 6.5.6
Tornado has cookie attribute injection via .RequestHandler.set_cookie
- Affected
- <6.5.5
- Fixed in
- 6.5.5
Tornado is vulnerable to DoS due to too many multipart parts
- Affected
- <6.5.5
- Fixed in
- 6.5.5
Tornado has incomplete validation of cookie attributes
- Affected
- <6.5.5
- Fixed in
- 6.5.5
Tornado vulnerable to excessive logging caused by malformed multipart form data
- Affected
- <6.5
- Fixed in
- 6.5
Tornado has an HTTP cookie parsing DoS vulnerability
- Affected
- <6.4.2
- Fixed in
- 6.4.2
Tornado has a CRLF injection in CurlAsyncHTTPClient headers
- Affected
- <6.4.1
- Fixed in
- 6.4.1
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in tornado
- Affected
- <6.4.1
- Fixed in
- 6.4.1
Tornado vulnerable to HTTP request smuggling via improper parsing of `Content-Length` fields and chunk lengths
- Affected
- <6.3.3
- Fixed in
- 6.3.3
Open redirect in Tornado
- Affected
- <6.3.2
- Fixed in
- 6.3.2
Every tornado 4.0.x release
Affected: 4.0.0 to 4.0.2. Latest tornado: 6.6.1.
| Version | Known advisories |
|---|---|
| tornado 4.0.2 | CVE-2026-126347, CVE-2026-115927, CVE-2026-116578, CVE-2026-116577, CVE-2026-103261, CVE-2026-103262, CVE-2026-103263, CVE-2026-82397, CVE-2026-91990, CVE-2025-67726, CVE-2025-67725, CVE-2025-67724, CVE-2026-91992, CVE-2026-49853, CVE-2026-49855, CVE-2026-49854, CVE-2026-35536, CVE-2026-31958, CVE-2026-35536, CVE-2025-47287, CVE-2024-52804, CVE-2024-58384, CVE-2024-14029, CVE-2023-54397, CVE-2023-28370 |
| tornado 4.0.1 | CVE-2026-126347, CVE-2026-115927, CVE-2026-116578, CVE-2026-116577, CVE-2026-103261, CVE-2026-103262, CVE-2026-103263, CVE-2026-82397, CVE-2026-91990, CVE-2025-67726, CVE-2025-67725, CVE-2025-67724, CVE-2026-91992, CVE-2026-49853, CVE-2026-49855, CVE-2026-49854, CVE-2026-35536, CVE-2026-31958, CVE-2026-35536, CVE-2025-47287, CVE-2024-52804, CVE-2024-58384, CVE-2024-14029, CVE-2023-54397, CVE-2023-28370 |
| tornado 4.0.0 | CVE-2026-126347, CVE-2026-115927, CVE-2026-116578, CVE-2026-116577, CVE-2026-103261, CVE-2026-103262, CVE-2026-103263, CVE-2026-82397, CVE-2026-91990, CVE-2025-67726, CVE-2025-67725, CVE-2025-67724, CVE-2026-91992, CVE-2026-49853, CVE-2026-49855, CVE-2026-49854, CVE-2026-35536, CVE-2026-31958, CVE-2026-35536, CVE-2025-47287, CVE-2024-52804, CVE-2024-58384, CVE-2024-14029, CVE-2023-54397, CVE-2023-28370 |
Which of your client projects are still on tornado 4.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact tornado version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other tornado versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.