CVE-2026-115927 tornadoweb CVE debrief

Who should care

Tornado users, administrators of web applications using Tornado, and security teams responsible for assessing and mitigating vulnerabilities in web infrastructure should be aware of this vulnerability. They should assess exposure, prioritize upgrading to version 6.6 or later, and consider temporary mitigations. The vulnerability requires verification of affected versions and attack scenarios.

Why it matters

CVE-2026-115927 is a medium-severity vulnerability in Tornado that can lead to event loop blocking and memory exhaustion. Defenders should assess exposure, prioritize upgrading to version 6.6 or later, and consider temporary mitigations. The vulnerability requires verification of affected versions and attack scenarios.

• Event loop blocking can lead to denial of service for all connections served by the affected process
• Excessive memory use can result in process crashes or slowdowns
• No authentication is required to exploit this vulnerability
• Verification of affected versions and attack scenarios is necessary

Technical summary

Tornado's handling of chunked HTTP/1.1 bodies can lead to event loop blocking and excessive memory use when processing many small chunks. This issue affects all Tornado HTTP servers when receiving request bodies for handlers that read them, without requiring authentication. The problem arises when a client sends a body made of millions of 1-byte chunks, which blocks the event loop for the entire time it takes to parse the body. Lowering max_body_size reduces but does not eliminate the issue. A body near the default max_body_size of 100 MB can block the process for close to a minute.

Defensive priority

Tornado users should assess exposure, prioritize upgrading to version 6.6 or later, and consider lowering max_body_size as a temporary mitigation.

Recommended defensive actions

• Assess exposure by checking if Tornado versions prior to 6.6 are in use
• Prioritize upgrading to Tornado version 6.6 or later
• Consider lowering max_body_size as a temporary mitigation
• Monitor for unusual request patterns that could indicate exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, but affected versions and specific attack scenarios require verification from official sources. The vulnerability requires verification of affected versions and attack scenarios. Official sources should be consulted for detailed information on affected versions and potential mitigations. The CVE Program record and NIST NVD detail page offer additional context.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.