CVE-2026-49855

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Tornado is a Python web framework and asynchronous networking library. Prior to 6.5.6, Tornado gzip decompression routines processed limited-size chunks but did not enforce an overall limit on accumulated decompressed chunks, allowing a malicious server accessed by SimpleAsyncHTTPClient or an HTTPServer configured with decompress_request=True to consume effectively unlimited memory. This issue is fixed in version 6.5.6.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

June 15, 2026

Last Modified

July 16, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

tornado AsyncHTTPClient accumulates decompressed chunks without size limit (gzip bomb) · Advisory · tornadoweb/tornado · GitHub

https://github.com/tornadoweb/tornado/security/advisories/GHSA-mgf9-4vpg-hj56
github_pr

Combined changes for release 6.5.6

Fix merged in tornadoweb/tornado PR #3626 on 2026-05-27 — awaiting tagged release

https://github.com/tornadoweb/tornado/pull/3626
github_commit

commit ff808b33adc5 (tornadoweb/tornado)

Fix landed in tornadoweb/tornado commit ff808b33adc5 — awaiting tagged release

https://github.com/tornadoweb/tornado/commit/ff808b33adc52d89a549376a5e3628e92abbc8ff

Vendor Advisories for CVE-2026-49855(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-tornado6.1.0-1 ... 6.5.5-4 (28 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-tornado6.2.0-3 ... 6.5.5-4 (23 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-tornado6.4.2-3 ... 6.5.5-4 (12 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-tornado6.4.2-3 ... 6.5.5-4 (10 versions)
PyPI(1)
PackageVulnerable rangeFixed inDependents
tornado0.2 ... 6.5b1 (81 versions)6.5.6

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 23:32 UTCEG score recompute
  3. 2026-08-23 09:44 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 07:27 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 08:40 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 13:14 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 22:24 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 10:15 UTCEG score recompute
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 10:20 UTCEG score recompute
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-13 22:03 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 17:48 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 19:40 UTCEG score recompute
  24. 2026-08-11 08:32 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 42 more
  1. 2026-08-09 23:20 UTCEG score recompute
  2. 2026-08-09 13:46 UTCEPSS rescore
  3. 2026-08-09 01:12 UTCEG score recompute
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-08 03:03 UTCEG score recompute
  6. 2026-08-06 17:51 UTCEG score recompute
  7. 2026-08-06 13:47 UTCEPSS rescore
  8. 2026-08-05 19:40 UTCEG score recompute
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-04 15:42 UTCEG score recompute
  11. 2026-08-04 15:10 UTCEPSS rescore
  12. 2026-08-04 10:39 UTCEPSS rescore
  13. 2026-08-03 20:01 UTCEG score recompute
  14. 2026-08-03 10:36 UTCEPSS rescore
  15. 2026-08-02 06:57 UTCEG score recompute
  16. 2026-08-02 02:27 UTCEPSS rescore
  17. 2026-08-01 08:49 UTCEG score recompute
  18. 2026-08-01 04:16 UTCEPSS rescore
  19. 2026-07-30 23:53 UTCEG score recompute
  20. 2026-07-30 16:28 UTCEPSS rescore
  21. 2026-07-30 05:10 UTCEG score recompute
  22. 2026-07-30 01:30 UTCEPSS rescore
  23. 2026-07-29 03:24 UTCEG score recompute
  24. 2026-07-28 15:37 UTCEPSS rescore
  25. 2026-07-28 01:52 UTCEG score recompute
  26. 2026-07-26 20:12 UTCEG score recompute
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-25 14:18 UTCEPSS rescore
  29. 2026-07-24 14:18 UTCEPSS rescore
  30. 2026-07-23 14:18 UTCEPSS rescore
  31. 2026-07-23 03:18 UTCEG score recompute
  32. 2026-07-22 14:08 UTCEPSS rescore
  33. 2026-07-21 15:25 UTCEPSS rescore
  34. 2026-07-20 17:08 UTCEPSS rescore
  35. 2026-07-19 14:31 UTCEPSS rescore
  36. 2026-07-19 14:31 UTCEPSS rescore
  37. 2026-07-19 02:29 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-16 17:03 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 16:57 UTCEPSS rescore
  42. 2026-06-15 20:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49855?
CVE-2026-49855 is a high vulnerability published on June 15, 2026. Tornado is a Python web framework and asynchronous networking library. Prior to 6.5.6, Tornado gzip decompression routines processed limited-size chunks but did not enforce an overall limit on accumulated decompressed chunks, allowing a malicious server accessed by SimpleAsyncHTTPClient or an…
When was CVE-2026-49855 disclosed?
CVE-2026-49855 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49855 actively exploited?
CVE-2026-49855 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.3% of all scored CVEs.
What is the CVSS score of CVE-2026-49855?
CVE-2026-49855 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-49855?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49855, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49855

Explore →

Is Your Infrastructure Affected by CVE-2026-49855?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.