CVE-2026-49855 tornadoweb CVE debrief

Who should care

Users of Tornado versions prior to 6.5.6 should update to the latest version to prevent potential memory consumption attacks. This includes operators, platform administrators, vulnerability management teams, and security teams who use Tornado in their applications.

Technical summary

Tornado's gzip decompression routines processed limited-size chunks but did not enforce an overall limit on accumulated decompressed chunks. This allowed a malicious server accessed by SimpleAsyncHTTPClient or an HTTPServer configured with decompress_request=True to consume effectively unlimited memory. The issue is fixed in version 6.5.6. Affected users should update to prevent potential memory consumption attacks.

Defensive priority

High priority should be given to updating Tornado to version 6.5.6 or later to prevent potential memory consumption attacks. Additionally, review and monitor server configurations, implement memory usage monitoring, and track exceptions for exposed assets.

Recommended defensive actions

• Update Tornado to version 6.5.6 or later
• Review and monitor server configurations for SimpleAsyncHTTPClient or HTTPServer with decompress_request=True
• Implement memory usage monitoring and limits for Tornado applications
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• 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 was published on 2026-07-14T21:17:02.437Z and was last modified on 2026-07-16T16:19:10.690Z. The NVD entry is currently Deferred. Evidence is limited to CVE and NVD details. Defenders should verify affected scope and vendor guidance with official sources.

Official resources