CVSS 4.0
6.9 mediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NMedium (6.9) in tornadoweb tornado. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in tornado 6.5.9.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Ltornado (PyPI): fixed in 6.5.9Explain CVE-2026-103261 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103261?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103261?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103261 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| tornadoweb tornado | before 6.5.9 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-3hv7-mjh2-fv65 | PyPI | tornado | <6.5.9 | 6.5.9 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | python-tornado | no fix listed | DEBIAN-CVE-2026-103261 |
| Debian | 14 | python-tornado | 6.6.0-1 | DEBIAN-CVE-2026-103261 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 and 4 more | python-tornado | no fix listed | UBUNTU-CVE-2026-103261 |
| SUSE | Linux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 more | python-tornado6 | 6.3.2-150400.9.32.1 | SUSE-SU-2026:5254-1 |
| Azure Linux | 3 | python-tornado | no fix listed | AZL-105372 |
| Alpaquita | 25, stream | py3-tornado | 6.5.10-r0 | BELL-CVE-2026-103261 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · Alpaquita.
Red Hat rates this Moderate.
A denial-of-service flaw of moderate impact was found in Tornado, a Python web framework and asynchronous networking library used by several Red Hat offerings, including Red Hat Enterprise Linux (pcs), Red Hat OpenShift Container Platform, and Fedora/EPEL community components. When processing incoming HTTP requests, Tornado does not limit the number of parameters parsed from the URL query string, although the equivalent POST-body parsing path is capped. A remote, unauthenticated attacker could send GET requests containing an excessive number of query parameters; parsing them is CPU-intensive work performed synchronously on the single-threaded event loop, which stalls the loop and significantly degrades response times for all clients sharing the same server process. The flaw affects availability only, with no confidentiality or integrity impact. Red Hat rates this flaw Moderate severity with CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), consistent with the upstream assessment. For Red Hat Enterprise Linux and OpenShift Container Platform, fixes are deferred because this Moderate-severity flaw has a CVSS score below 7.0 and no tracker is filed at that priority; the residual risk is degraded responsiveness of network-exposed Tornado-based services. For Fedora and EPEL community components, resolution is delegated to the community maintainers and a fix is being pursued.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Lightspeed Core | lightspeed-core/lightspeed-stack-rhel9 | Fix deferred | |
| Lightspeed Core | lightspeed-core/rag-tool-cpu-rhel9 | Fix deferred | |
| Lightspeed Core | lightspeed-core/rag-tool-cuda-12.9-rhel9 | Fix deferred | |
| Migration Toolkit for Applications 8 | mta/mta-solution-server-rhel9 | Out of support scope | |
| OpenShift Lightspeed | openshift-lightspeed/lightspeed-ocp-rag-rhel9 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-26/lightspeed-chatbot-rhel9 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-27/lightspeed-chatbot-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux 10 | python-tornado | Fix deferred | |
| Red Hat Enterprise Linux 10 | rhel10/keylime-registrar | Fix deferred | |
| Red Hat Enterprise Linux 10 | rhel10/keylime-verifier | Fix deferred | |
| Red Hat Enterprise Linux 8 | pcs | Fix deferred | |
| Red Hat Enterprise Linux 9 | python-tornado | Fix deferred | |
| Red Hat Enterprise Linux 9 | rhel9/keylime-registrar | Fix deferred | |
| Red Hat Enterprise Linux 9 | rhel9/keylime-verifier | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-cuda-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-gaudi-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-rocm-rhel9 | Fix deferred | |
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/disk-image-cuda-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-feature-server-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-llama-stack-core-rhel9 | Fix deferred | |
| 48 more in the JSON and on Red Hat's page. | |||
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-103261.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).