BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-31958High confidence

Tornado has a DoS due to too many multipart parts

tornadoweb · tornado

Official source article: GitHub GHSA-QJXF-F2MG-C6MC ↗. Check the applicable product and release in the original source.

8.7HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
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.49% 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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

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
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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-tornadoAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcepython-tornadoAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython-tornadoVendor fix publishedDebian records a fixed source-package version for this release.6.5.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython-tornadoVendor fix publishedDebian records a fixed source-package version for this release.6.5.5-1Debian 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.5Canonical 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.5.56.5.5OSV record ↗aggregator derived · 10 Sep 2026
piptornado<= 6.5.46.5.5GitHub advisory ↗upstream repository advisory · 8 Jun 2026
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-2026-31958 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitytornado-python: Tornado: Denial of Service via large multipart bodies
9 known affected

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

  • lightspeed-core/lightspeed-stack-rhel9 as a component of Lightspeed Core
  • lightspeed-core/rag-tool-rhel9 as a component of Lightspeed Core
  • pcs as a component of Red Hat Enterprise Linux 9
  • pcs-snmp as a component of Red Hat Enterprise Linux 9
  • pcs.src as a component of Red Hat Enterprise Linux 9
  • rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
  • rhelai3/bootc-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
  • rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
  • rhoai/odh-trustyai-ragas-lls-provider-dsp-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
Summary
A flaw was found in tornado-python. A remote attacker can exploit this vulnerability by sending a specially crafted, very large multipart body with numerous parts. Because the parsing of these large bodies occurs synchronously on the main thread, it can consume excessive resources, leading to a denial of service (DoS) for the application.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
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-2026-11323

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 actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Tornado is a Python web framework and asynchronous networking library. In versions of Tornado prior to 6.5.5, the only limit on the number of parts in multipart/form-data is the max_body_size setting (default 100MB). Since parsing occurs synchronously on the main thread, this creates the possibility of denial-of-service due to the cost of parsing very large multipart bodies with many parts. This vulnerability is fixed in 6.5.5.

What

Tornado is a Python web framework and asynchronous networking library. In versions of Tornado prior to 6.5.5, the only limit on the number of parts in multipart/form-data is the max_body_size setting (default 100MB). Since parsing occurs synchronously on the main thread, this creates the possibility of denial-of-service due to the cost of parsing very large multipart bodies with many parts. This vulnerability is fixed in 6.5.5.

Why

The product does not properly control the allocation and maintenance of a limited resource.

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. In versions of Tornado prior to 6.5.5, the only limit on the number of parts in multipart/form-data is the max_body_size setting (default 100MB). Since parsing occurs synchronously on the main thread, this creates the possibility of denial-of-service due to the cost of parsing very large multipart bodies with many parts. This vulnerability is fixed in 6.5.5.

Why

The product does not properly control the allocation and maintenance of a limited resource.

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 → Uncontrolled Resource Consumption → 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
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-400 ↗

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: 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.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
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-400
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2933Splunk SOAR: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk SOAR ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen SQL-Injection Angriff durchzuführen, um einen Cross-Site Scripting Angriff durchzuführen, und um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1112Red Hat Enterprise Linux (pcs): Schwachstelle ermöglicht Denial of Service

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

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

ord?id=CVE-2026-26996 Référence CVE CVE-2026-27024 https://www.cve.org/CVERecord?id=CVE-2026-27024 Référence CVE CVE-2026-27025 https://www.cve.org/CVERecord?id=CVE-2026-27025 Référence CVE CVE-2026-27026 https://www.cve.org/CVERecord?id=CVE-2026-27026 Référence CVE CVE-2026-27205 https://www.cve.org/CVERecord?id=CVE-2026-27205 Référence CVE CVE-2026-27903 https://www.cve.org/CVERecord?id=CVE-2026-27903 Référence CVE CVE-2026-27904 https://www.cve.org/CVERecord?id=CVE-2026-27904 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-30922 https://www.cve.org/CVERecord?id=CVE-2026-30922 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-33230 https://www.cve.org/CVERecord?id=CVE-2026-33230 Référence CVE CVE-2026-33231 https://www.cve.org/CVERecord?id=CVE-2026-33231 Référence CVE CVE-2026-33236 https://www.cve.org/CVERecord?id=CVE-2026-33236 Référence CVE CVE-2026-33416 https://www.cve.org/CVERecord?id=CVE-2026-33416 Référence CVE CVE-2026-34073 https://www.cve.org/CVERecord?id=CVE-2026-34073 Référence CVE CVE-2026-34197 https://www.cve.org/CVERecord?id=CVE-2026-34197 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-28755 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-29181 https://www.cve.org/CVERecord?id=CVE-2026-29181 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-30922 https://www.cve.org/CVERecord?id=CVE-2026-30922 Référence CVE CVE-2026-31789 https://www.cve.org/CVERecord?id=CVE-2026-31789 Référence CVE CVE-2026-31790 https://www.cve.org/CVERecord?id=CVE-2026-31790 Référence CVE CVE-2026-31898 https://www.cve.org/CVERecord?id=CVE-2026-31898 Référence CVE CVE-2026-31938 https://www.cve.org/CVERecord?id=CVE-2026-31938 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32280 https://www.cve.org/CVERecord?id=CVE-2026-32280 Référence CVE CVE-2026-32281 https://www.cve.org/CVERecord?id=CVE-2026-32281 Référence CVE CVE-2026-32283 https://www.cve.org/CVERecord?id=CVE-2026-32283 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-32647 https://www.cve.org/CVERecord?id=CVE-2026-32647 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-27904 Référence CVE CVE-2026-27980 https://www.cve.org/CVERecord?id=CVE-2026-27980 Référence CVE CVE-2026-28684 https://www.cve.org/CVERecord?id=CVE-2026-28684 Référence CVE CVE-2026-29057 https://www.cve.org/CVERecord?id=CVE-2026-29057 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-29786 https://www.cve.org/CVERecord?id=CVE-2026-29786 Référence CVE CVE-2026-30922 https://www.cve.org/CVERecord?id=CVE-2026-30922 Référence CVE CVE-2026-31802 https://www.cve.org/CVERecord?id=CVE-2026-31802 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-3304 https://www.cve.org/CVERecord?id=CVE-2026-3304 Référence CVE CVE-2026-33227 https://www.cve.org/CVERecord?id=CVE-2026-33227 Référence CVE CVE-2026-33532 https://www.cve.org/CVERecord?id=CVE-2026-33532 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-33814 https://www.cve.org/CVERecord?id=CVE-2026-33814 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2026-25679 Référence CVE CVE-2026-26007 https://www.cve.org/CVERecord?id=CVE-2026-26007 Référence CVE CVE-2026-26996 https://www.cve.org/CVERecord?id=CVE-2026-26996 Référence CVE CVE-2026-27142 https://www.cve.org/CVERecord?id=CVE-2026-27142 Référence CVE CVE-2026-27903 https://www.cve.org/CVERecord?id=CVE-2026-27903 Référence CVE CVE-2026-27904 https://www.cve.org/CVERecord?id=CVE-2026-27904 Référence CVE CVE-2026-29045 https://www.cve.org/CVERecord?id=CVE-2026-29045 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-29087 https://www.cve.org/CVERecord?id=CVE-2026-29087 Référence CVE CVE-2026-31958 https://www.cve.org/CVERecord?id=CVE-2026-31958 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-33186 https://www.cve.org/CVERecord?id=CVE-2026-33186 Référence CVE CVE-2026-33228 https://www.cve.org/CVERecord?id=CVE-2026-33228 Référence CVE CVE-2026-33671 https://www.cve.org/CVERecord?id=CVE-2026-33671 Référence CVE CVE-2026-33672 https://www.cve.org/CVERecord?id=CVE-2026-33672 Référence CVE CVE-2026-33750 https://www.cve.org/CVERecord?id=CVE-2026-33750 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-007561tornadowebのTornadoにおけるリソースの枯渇に関する脆弱性

TornadoはPythonのウェブフレームワークおよび非同期ネットワーキングライブラリです。バージョン6.5.5以前のTornadoでは、multipart/form-dataのパーツ数に対する唯一の制限がmax_body_size設定（デフォルト100MB）でした。パースはメインスレッドで同期的に行われるため、多数のパーツを含む非常に大きなmultipartボディの解析コストにより、サービス拒否（DoS）が発生する可能性があります。この脆弱性はバージョン6.5.5で修正されました。

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.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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 11 Mar 2026 · Last source change 1 Apr 2026, 14:32 UTC · CWE-400 · Uncontrolled Resource Consumption

CVE recordCVE.org · 5.2
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-2026-11323
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    lightspeed-core/lightspeed-stack-rhel9 as a component of Lightspeed Core; lightspeed-core/rag-tool-rhel9 as a component of Lightspeed Core; pcs as a component of Red Hat Enterprise Linux 9; pcs-snmp as a component of Red Hat Enterprise Linux 9; pcs.src as a component of Red Hat Enterprise Linux 9; rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/bootc-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhoai/odh-trustyai-ragas-lls-provider-dsp-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · Fixed: python-tornado-0:4.2.1-5.el7_9.3.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:4.2.1-5.el7_9.3.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:4.2.1-5.el7_9.3.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:4.2.1-5.el7_9.3.src as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:4.2.1-5.el7_9.3.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-debuginfo-0:4.2.1-5.el7_9.3.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-debuginfo-0:4.2.1-5.el7_9.3.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-debuginfo-0:4.2.1-5.el7_9.3.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-debuginfo-0:4.2.1-5.el7_9.3.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-doc-0:4.2.1-5.el7_9.3.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-doc-0:4.2.1-5.el7_9.3.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-doc-0:4.2.1-5.el7_9.3.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-doc-0:4.2.1-5.el7_9.3.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:6.4.2-1.el10_0.2.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-debugsource-0:6.4.2-1.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-debugsource-0:6.4.2-1.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-debugsource-0:6.4.2-1.el10_0.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-debugsource-0:6.4.2-1.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-0:6.4.2-1.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-0:6.4.2-1.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-0:6.4.2-1.el10_0.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-0:6.4.2-1.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-debuginfo-0:6.4.2-1.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-debuginfo-0:6.4.2-1.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-debuginfo-0:6.4.2-1.el10_0.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-debuginfo-0:6.4.2-1.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-0:6.5.5-1.el10_1.1.src as a component of Red Hat Enterprise Linux AppStream (v. 10); python-tornado-debugsource-0:6.5.5-1.el10_1.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); python-tornado-debugsource-0:6.5.5-1.el10_1.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); python-tornado-debugsource-0:6.5.5-1.el10_1.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); and 223 more
    After
    lightspeed-core/lightspeed-stack-rhel9 as a component of Lightspeed Core; lightspeed-core/rag-tool-rhel9 as a component of Lightspeed Core; pcs as a component of Red Hat Enterprise Linux 9; pcs-snmp as a component of Red Hat Enterprise Linux 9; pcs.src as a component of Red Hat Enterprise Linux 9; rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/bootc-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; rhoai/odh-trustyai-ragas-lls-provider-dsp-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · Fixed: python-tornado-0:4.2.1-5.el7_9.3.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:4.2.1-5.el7_9.3.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:4.2.1-5.el7_9.3.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:4.2.1-5.el7_9.3.src as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:4.2.1-5.el7_9.3.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-debuginfo-0:4.2.1-5.el7_9.3.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-debuginfo-0:4.2.1-5.el7_9.3.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-debuginfo-0:4.2.1-5.el7_9.3.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-debuginfo-0:4.2.1-5.el7_9.3.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-doc-0:4.2.1-5.el7_9.3.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-doc-0:4.2.1-5.el7_9.3.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-doc-0:4.2.1-5.el7_9.3.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-doc-0:4.2.1-5.el7_9.3.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7 ELS); python-tornado-0:6.4.2-1.el10_0.2.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-debugsource-0:6.4.2-1.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-debugsource-0:6.4.2-1.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-debugsource-0:6.4.2-1.el10_0.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-debugsource-0:6.4.2-1.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-0:6.4.2-1.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-0:6.4.2-1.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-0:6.4.2-1.el10_0.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-0:6.4.2-1.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-debuginfo-0:6.4.2-1.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-debuginfo-0:6.4.2-1.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-debuginfo-0:6.4.2-1.el10_0.2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python3-tornado-debuginfo-0:6.4.2-1.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); python-tornado-0:6.5.5-1.el10_1.1.src as a component of Red Hat Enterprise Linux AppStream (v. 10); python-tornado-debugsource-0:6.5.5-1.el10_1.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); python-tornado-debugsource-0:6.5.5-1.el10_1.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); python-tornado-debugsource-0:6.5.5-1.el10_1.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); and 236 more
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 6.5.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 6.5.5 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-11323↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-QJXF-F2MG-C6MC↗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-2026-31958 · cve.blacktree.nl