CVE-2026-115927VulnerabilityPublished 26 Oct 2026Updated 6 Nov 2026

Python tornado: Prior to 6.6.0, Tornado decodes HTTP/1.1 chunked transfer encoding by processing body data that has

Affects python-tornadoSource GCVE Database

Compare

Authoritative record:CVE-2026-115927· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 6.6.0 : update python-tornado when convenient.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 3.1 base score

5.3Medium

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	5.3

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

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

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

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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Oct 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 6 Nov 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

Affected software

Product	Affected	Fixed in
Ubuntu 26.10python-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=stonking`Other threats	Affected 6.5.4-0.1 – 6.5.5-5ubuntu1.2 6 affected builds	Fixed in–
Ubuntu 26.04 LTSpython-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=resolute`Other threats	Affected 6.4.2-3 – 6.5.4-0.1ubuntu0.3 6 affected builds	Fixed in–
Ubuntu 24.04 LTSpython-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=noble`Other threats	Affected 6.3.2-1 – 6.4.0-1ubuntu0.7 10 affected builds	Fixed in–
Ubuntu Pro 22.04 LTSpython-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=esm-apps/jammy`Other threats	Affected 6.1.0-1build1 – 6.1.0-3ubuntu0.1~esm7 10 affected builds	Fixed in–
Ubuntu Pro 20.04 LTSpython-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=esm-apps/focal`Other threats	Affected 5.1.1-4ubuntu1 – 6.0.3+really5.1.1-3ubuntu0.1~esm8 11 affected builds	Fixed in–
Ubuntu Pro 18.04 LTSpython-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=esm-apps/bionic`Other threats	Affected 4.5.1-2.1~build2 – 4.5.3-1ubuntu0.2+esm5 10 affected builds	Fixed in–

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

AI-suggested

Upgrade Tornado to version 6.6.0 or later, where this vulnerability is fixed. No other mitigations are indicated. Lowering max_body_size only limits request duration but does not prevent the event loop monopolization. Users should apply the official fix to fully remediate the issue.

Description

Tornado versions prior to 6.6.0 have a vulnerability in HTTP/1.1 chunked transfer encoding decoding where the process event loop can be monopolized by a remote unauthenticated attacker sending many one-byte chunks. This stalls other connections and can cause high memory consumption due to chunk retention. The issue affects both server handlers and the SimpleAsyncHTTPClient. The vulnerability is fixed in Tornado 6.6.0.

Impact

An unauthenticated remote attacker can cause denial of service by monopolizing the Tornado process event loop through sending many small HTTP chunks, stalling all other connections served by that process. Memory consumption can also be significantly increased due to chunk retention, potentially leading to resource exhaustion. There is no impact on confidentiality or integrity. The CVSS score is 5.3 (medium severity) reflecting the denial of service impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 21:03 UTC

Technical details

References

Community reviews

Related threats