CVE-2025-67724VulnerabilityPublished 12 Dec 2025Updated 6 Nov 2026

Python tornado:

Affects python-tornadoSource GCVE Database

Authoritative record:CVE-2025-67724· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium · fixed in 6.0.3+really5.1.1-3ubuntu0.1~esm3 : update python-tornado when convenient.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.0.3+really5.1.1-3ubuntu0.1~esm3, 6.1.0-3ubuntu0.1~esm4, 6.4.0-1ubuntu0.4 +1

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

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

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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Dec 2025
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

Upgrade to a fixed release listed under Affected software.

Patches and advisories

ubuntu.com/security/notices/USN-7950-1 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Ubuntu 25.10python-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=questing`Other threats	Affected <6.4.2-3ubuntu0.2	Fixed in 6.4.2-3ubuntu0.2
Ubuntu 24.04 LTSpython-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=noble`Other threats	Affected <6.4.0-1ubuntu0.4	Fixed in 6.4.0-1ubuntu0.4
Ubuntu Pro 22.04 LTSpython-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=esm-apps/jammy`Other threats	Affected <6.1.0-3ubuntu0.1~esm4	Fixed in 6.1.0-3ubuntu0.1~esm4
Ubuntu Pro 20.04 LTSpython-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=esm-apps/focal`Other threats	Affected <6.0.3+really5.1.1-3ubuntu0.1~esm3	Fixed in 6.0.3+really5.1.1-3ubuntu0.1~esm3
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–
Ubuntu Pro 16.04 LTSpython-tornado`pkg:deb/ubuntu/python-tornado?arch=source&distro=esm-infra-legacy/xenial`Other threats	Affected 4.2.1-1ubuntu2 – 4.2.1-1ubuntu3.1+esm5 8 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

A fix is available in Tornado version 6.5.3 and in updated Ubuntu packages as detailed in the Ubuntu security notice USN-7950-1. Users should update to the fixed versions listed for their respective Ubuntu releases or upgrade Tornado to version 6.5.3 or later. Standard system updates on supported Ubuntu versions will apply the necessary patches. No additional mitigation is required once patched.

Description

Python Tornado versions 6.5.2 and below improperly handle the supplied reason phrase in HTTP headers without escaping it. This flaw allows injection of malicious content into HTTP headers or the default error page, potentially enabling HTTP header injection or cross-site scripting (XSS) attacks. The vulnerability affects the reason argument used in RequestHandler.set_status and tornado.web.HTTPError. The issue is fixed in Tornado version 6.5.3.

Impact

An attacker can exploit this vulnerability by supplying malicious input to the reason phrase argument, leading to HTTP header injection or cross-site scripting (XSS) attacks. This can compromise the security of web applications using affected Tornado versions by injecting unauthorized headers or executing arbitrary scripts in users' browsers. The CVSS score is 6.1 (medium severity) with impact on confidentiality and integrity but no availability impact.

References

Community reviews

Loading reviews…