Skip to main content
VulnerabilityPublished Updated

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

Affects livereloadSource GCVE Database

0
Compare
Authoritative record:CVE-2026-49855· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.7.1_2 soon.

Data as of 30 Oct 2026, 06:44 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.7.1_2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade livereload to 2.7.1_2.

Affected software

ProductAffectedFixed in
Homebrewlivereloadpkg:brew/livereloadOther threatsAffected
  • >=2.7.1 <2.7.1_2
Fixed in
  • 2.7.1_2

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

AI-suggested

Upgrade to Tornado version 2.7.1_2 or later where the issue is fixed. Until then, mitigate by setting decompress_response=False in SimpleAsyncHTTPClient or by using CurlAsyncHTTPClient instead. No other actions are required.

Description

Tornado's AsyncHTTPClient in Livereload versions >=2.7.1 and <2.7.1_2 has a vulnerability where gzip decompression accumulates decompressed chunks without an overall size limit, allowing a malicious server to cause excessive memory consumption (a gzip bomb). This issue does not affect HTTPServer by default unless decompress_request=True is set. The vulnerability is fixed in version 2.7.1_2 by enforcing max_body_size checks on both compressed and decompressed data.

References

Community reviews

Loading reviews…