BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-47287High confidence

Tornado vulnerable to excessive logging caused by malformed multipart form data

tornadoweb · tornado

Official source article: GitHub GHSA-7CX3-6M66-7C5M ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.74% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs tornadoweb tornado and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcepython-tornadoVendor fix publishedDebian records a fixed source-package version for this release.6.4.2-2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcepython-tornadoVendor fix publishedDebian records a fixed source-package version for this release.6.2.0-3+deb12u2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython-tornadoVendor fix publishedDebian records a fixed source-package version for this release.6.4.2-2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython-tornadoVendor fix publishedDebian records a fixed source-package version for this release.6.4.2-2Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivepython-tornadoVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.6.4.0-1ubuntu0.2Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPItornadoECOSYSTEM: introduced 0; fixed 6.56.5OSV record ↗aggregator derived · 10 Sep 2026
piptornado< 6.56.5GitHub advisory ↗upstream repository advisory · 29 May 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-47287 · CSAF 2.0 · revision 42 · interimSUSE Product Security TeamCVE-2025-47287
51 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • python-tornado as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • python2-tornado as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • python3-tornado as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • python-tornado as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • python2-tornado as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • python3-tornado as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • python-tornado as component of SUSE Linux Enterprise High Performance Computing 15
  • python2-tornado as component of SUSE Linux Enterprise High Performance Computing 15
  • python3-tornado as component of SUSE Linux Enterprise High Performance Computing 15
  • python-tornado as component of SUSE Linux Enterprise Server 15 SP1-LTSS
  • python2-tornado as component of SUSE Linux Enterprise Server 15 SP1-LTSS
  • python3-tornado as component of SUSE Linux Enterprise Server 15 SP1-LTSS
Summary
Tornado is a Python web framework and asynchronous networking library. When Tornado's ``multipart/form-data`` parser encounters certain errors, it logs a warning but continues trying to parse the remainder of the data. This allows remote attackers to generate an extremely high volume of logs, constituting a DoS attack. This DoS is compounded by the fact that the logging subsystem is synchronous. All versions of Tornado prior to 6.5.0 are affected. The vulnerable parser is enabled by default. Upgrade to Tornado version 6.50 to receive a patch. As a workaround, risk can be mitigated by blocking `Content-Type: multipart/form-data` in a proxy.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-15444

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

Tornado is a Python web framework and asynchronous networking library. When Tornado's ``multipart/form-data`` parser encounters certain errors, it logs a warning but continues trying to parse the remainder of the data. This allows remote attackers to generate an extremely high volume of logs, constituting a DoS attack. This DoS is compounded by the fact that the logging subsystem is synchronous. All versions of Tornado prior to 6.5.0 are affected. The vulnerable parser is enabled by default. Upgrade to Tornado version 6.50 to receive a patch. As a workaround, risk can be mitigated by blocking `Content-Type: multipart/form-data` in a proxy.

What

Tornado is a Python web framework and asynchronous networking library. When Tornado's ``multipart/form-data`` parser encounters certain errors, it logs a warning but continues trying to parse the remainder of the data. This allows remote attackers to generate an extremely high volume of logs, constituting a DoS attack. This DoS is compounded by the fact that the logging subsystem is synchronous. All versions of Tornado prior to 6.5.0 are affected. The vulnerable parser is enabled by default. Upgrade to Tornado version 6.50 to receive a patch. As a workaround, risk can be mitigated by blocking `Content-Type: multipart/form-data` in a proxy.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Tornado is a Python web framework and asynchronous networking library. When Tornado's ``multipart/form-data`` parser encounters certain errors, it logs a warning but continues trying to parse the remainder of the data. This allows remote attackers to generate an extremely high volume of logs, constituting a DoS attack. This DoS is compounded by the fact that the logging subsystem is synchronous. All versions of Tornado prior to 6.5.0 are affected. The vulnerable parser is enabled by default. Upgrade to Tornado version 6.50 to receive a patch. As a workaround, risk can be mitigated by blocking `Content-Type: multipart/form-data` in a proxy.

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Allocation of Resources Without Limits or Throttling → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-770 ↗

CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-770
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-1143Red Hat Enterprise Linux (python-tornado): Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0901Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2024-47081 Référence CVE CVE-2024-52804 https://www.cve.org/CVERecord?id=CVE-2024-52804 Référence CVE CVE-2024-6485 https://www.cve.org/CVERecord?id=CVE-2024-6485 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-14505 https://www.cve.org/CVERecord?id=CVE-2025-14505 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-15599 https://www.cve.org/CVERecord?id=CVE-2025-15599 Référence CVE CVE-2025-23165 https://www.cve.org/CVERecord?id=CVE-2025-23165 Référence CVE CVE-2025-47287 https://www.cve.org/CVERecord?id=CVE-2025-47287 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-59436 https://www.cve.org/CVERecord?id=CVE-2025-59436 Référence CVE CVE-2025-59437 https://www.cve.org/CVERecord?id=CVE-2025-59437 Référence CVE CVE-2025-59471 https://www.cve.org/CVERecord?id=CVE-2025-59471 Référence CVE CVE-2025-59472 https://www.cve.org/CVERecord?id=CVE-2025-59472 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=CVE-2025-62718 Référence CVE CVE-2025-6493 https://www.cve.org/CVERecord?id=CVE-2025-6493 Référence CVE CVE-2025-66221 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0118Multiples vulnérabilités dans les produits Splunk

De multiples vulnérabilités ont été découvertes dans les produits Splunk. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1131Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2025-39761 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39955 https://www.cve.org/CVERecord?id=CVE-2025-39955 Référence CVE CVE-2025-41234 https://www.cve.org/CVERecord?id=CVE-2025-41234 Référence CVE CVE-2025-41235 https://www.cve.org/CVERecord?id=CVE-2025-41235 Référence CVE CVE-2025-4447 https://www.cve.org/CVERecord?id=CVE-2025-4447 Référence CVE CVE-2025-46653 https://www.cve.org/CVERecord?id=CVE-2025-46653 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47287 https://www.cve.org/CVERecord?id=CVE-2025-47287 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2025-47907 Référence CVE CVE-2025-47913 https://www.cve.org/CVERecord?id=CVE-2025-47913 Référence CVE CVE-2025-48734 https://www.cve.org/CVERecord?id=CVE-2025-48734 Référence CVE CVE-2025-50059 https://www.cve.org/CVERecord?id=CVE-2025-50059 Référence CVE CVE-2025-5187 https://www.cve.org/CVERecord?id=CVE-2025-5187 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0760Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2025-36097 Référence CVE CVE-2025-37749 https://www.cve.org/CVERecord?id=CVE-2025-37749 Référence CVE CVE-2025-37799 https://www.cve.org/CVERecord?id=CVE-2025-37799 Référence CVE CVE-2025-4138 https://www.cve.org/CVERecord?id=CVE-2025-4138 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-4435 https://www.cve.org/CVERecord?id=CVE-2025-4435 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 Référence CVE CVE-2025-46762 https://www.cve.org/CVERecord?id=CVE-2025-46762 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47287 https://www.cve.org/CVERecord?id=CVE-2025-47287 Référence CVE CVE-2025-48050 https://www.cve.org/CVERecord?id=CVE-2025-48050 Référence CVE CVE-2025-48068 https://www.cve.org/CVERecord?id=CVE-2025-48068 Référence CVE CVE-2025-48734 https://www.cve.org/CVERecord?id=CVE-2025-48734 Référence CVE CVE-2025-48976 https://www.cve.org/CVERecord?id=CVE-2025-48976 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-50182 https://www.cve.org/CVERecord?id=CVE-2025-50182 Référence CVE CVE-2025-52999 https://www.cve.org/CVERecord?id=CVE-2025-52999 Référence CVE CVE-2025-53547 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-023180Debian等の複数ベンダの製品における制限またはスロットリング無しのリソースの割り当てに関する脆弱性

Tornadoは、PythonのWebフレームワークおよび非同期ネットワーキングライブラリです。Tornadoの「multipart/form-data」パーサは、特定のエラーに遭遇した際、警告をログに記録した後もデータの残りの解析処理を続行します。この動作により、リモートの攻撃者が非常に大量のログを生成でき、サービス拒否（DoS）攻撃が発生する可能性があります。また、ログ記録サブシステムが同期的であるため、このDoSがさらに深刻化する場合があります。Tornadoのバージョン6.5.0未満の全てが影響を受けており、脆弱なパーサはデフォルトで有効化されています。パッチを適用するには、Tornadoをバージョン6.5.0へアップグレードしてください。回避策として、プロキシで「Content-Type: multipart/form-data」をブロックすることでリスクを軽減できます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 15 May 2025 · Last source change 29 May 2025, 06:04 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-15444
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-15444↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference · GitHub GHSA-7CX3-6M66-7C5M↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-47287 · cve.blacktree.nl