VulnerabilityPublished 13 Aug 2026Updated 30 Oct 2026

CVE-2026-49855: Snakeviz · tornado AsyncHTTPClient accumulates decompressed chunks without size limit (gzip bomb)

Affects snakevizSource GCVE Database

Compare

Authoritative record:CVE-2026-49855· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.2.2_4 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.2.2_4

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade snakeviz to 2.2.2_4.

Affected software

Product	Affected	Fixed in
Homebrewsnakeviz`pkg:brew/snakeviz`Other threats	Affected >=2.2.0 <2.2.2_4	Fixed in 2.2.2_4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Tornado 6.5.6. Users should upgrade to this version or later to resolve the issue. Until then, mitigation options include setting decompress_response=False in SimpleAsyncHTTPClient or using CurlAsyncHTTPClient instead. HTTPServer users should ensure decompress_request is not enabled unless necessary.

Description

A vulnerability in Tornado's AsyncHTTPClient gzip decompression allows a malicious server to cause excessive memory consumption by sending a crafted response that decompresses to an unlimited size. This affects SimpleAsyncHTTPClient in its default configuration and HTTPServer if decompress_request=True is set. The issue is fixed in Tornado 6.5.6 by enforcing max_body_size checks on both compressed and decompressed data. Prior to patching, mitigation includes disabling response decompression or using CurlAsyncHTTPClient.

Impact

An attacker controlling a malicious server can exploit this vulnerability to cause a denial of service by consuming excessive memory on clients using Tornado's SimpleAsyncHTTPClient with default decompression enabled. This can lead to application crashes or degraded performance. HTTPServer is only vulnerable if decompress_request is explicitly enabled. No confidentiality or integrity impacts are reported.

Summary

Tornado's gzip decompression routines process data in limited-size chunks but lack an overall limit on the total decompressed size accumulated. While the compressed size is limited, the decompressed output can grow without bound, enabling a malicious server to exhaust memory when accessed via SimpleAsyncHTTPClient with default settings. HTTPServer is unaffected unless decompress_request=True is enabled. The vulnerability is addressed in Tornado 6.5.6, which enforces max_body_size limits on both compressed and decompressed response sizes. Until upgrading, users can mitigate by disabling decompression or switching to CurlAsyncHTTPClient.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 06:04 UTC

Technical details

References

Community reviews

Related threats