No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 27 Oct 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 27 Oct 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-1322 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Mon, 26 Oct 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tornadoweb
Tornadoweb tornado |
|
| Vendors & Products |
Tornadoweb
Tornadoweb tornado |
Mon, 26 Oct 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Tornado is a Python web framework and asynchronous networking library. Prior to 6.6.0, Tornado decodes HTTP/1.1 chunked transfer encoding by processing body data that has already arrived without yielding to the event loop. A remote unauthenticated peer can send millions of one-byte chunks to monopolize the process event loop and stall every other connection served by that process, while lowering max_body_size only limits the duration of each request. For handlers that do not use @stream_request_body, retaining each chunk as a separate object can consume roughly twenty times the received body size, and SimpleAsyncHTTPClient has the same event-loop behavior when reading a response from a malicious server. This issue is fixed in version 6.6.0. | |
| Title | Tornado: Event loop blocking and excess memory use from chunked bodies with many small chunks | |
| Weaknesses | CWE-400 CWE-770 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-27T14:18:44.227Z
Reserved: 2026-10-23T20:21:45.108Z
Link: CVE-2026-115927
Updated: 2026-10-27T13:45:57.275Z
Status : Deferred
Published: 2026-10-26T20:17:52.397
Modified: 2026-10-27T15:16:32.303
Link: CVE-2026-115927
OpenCVE Enrichment
Updated: 2026-10-27T13:45:02Z