Skip to content
CVE Alert: CVE-2026-103262 – tornadoweb

CVE Alert: CVE-2026-103262 – tornadoweb

Redpacketsecurity •admin • October 1, 2026

Tornado versions before 6.5.9 contain an unbounded memory accumulation vulnerability in CurlAsyncHTTPClient that allows remote attackers to cause denial of service by sending a compressed response. Attackers can send a gzip-encoded decompression bomb that accumulates in memory without size limits, causing the application process to be killed by out-of-memory conditions.

**Risk verdict:** High availability risk where the affected asynchronous HTTP client is in use; exploitation status is unconfirmed because KEV, SSVC, PoC and EPSS data were not provided.

**Why this matters:** A crafted compressed response can exhaust process memory and cause service failure, potentially disrupting customer-facing APIs or dependent workflows. The expected impact is availability loss rather than data theft or modification; repeated requests could increase recovery costs and service disruption.

**Most likely attack path:** An unauthenticated attacker can deliver a malicious response over the network without user interaction, with low attack complexity. The practical precondition is that the application uses the vulnerable client to fetch a response the attacker can influence, such as from a user-supplied URL or compromised upstream; impact appears confined to the affected service, limiting direct lateral movement.

**Who is most exposed:** Python asynchronous web services that use this framework’s Curl-based HTTP client for proxying, URL previews, webhooks or other external fetches are the priority to check.

Alert on sharp process-memory growth during outbound HTTP requests.

Correlate gzip response headers with large decompressed-byte counts.

Review OOM-killer events, container restarts and abrupt worker exits.

Identify requests to untrusted or user-controlled upstream hosts.

Mitigation and prioritisation

Upgrade to the fixed release; prioritise services using the affected client.

If upgrade is delayed, disable that client or restrict it to trusted destinations.

Enforce decompressed-response size limits and bound request concurrency.

Test expected compressed-response workloads and monitor memory after deployment.

KEV and EPSS status are unavailable, so the priority-1 trigger cannot be assessed.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

Extracted Entities