cve.bz

CVE-2026-103263 tornadoweb tornado: Link Following

8.2 highEPSS 0.5%Fix available

High (8.2) in tornadoweb tornado. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in tornado 6.5.9.

On this page
Tornado before 6.5.9 contains a path traversal vulnerability in StaticFileHandler that follows symbolic links inside the static root without confirming the resolved target stays within it. When a symlink pointing outside the static directory exists inside it, unauthenticated attackers can request it to read files such as configuration files, private keys, and application secrets accessible to the process user.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 45th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-103263 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103263?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103263?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-103263 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
tornadoweb tornadobefore 6.5.9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c2m8-h5v5-343rPyPItornado<6.5.96.5.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13python-tornadono fix listedDEBIAN-CVE-2026-103263
Debian14python-tornado6.6.0-1DEBIAN-CVE-2026-103263
Ubuntu24.04:LTSpython-tornado6.4.0-1ubuntu0.8UBUNTU-CVE-2026-103263 USN-8952-1 USN-8952-2 USN-8952-3
Ubuntu26.04:LTSpython-tornado6.5.4-0.1ubuntu0.4UBUNTU-CVE-2026-103263 USN-8952-1 USN-8952-2 USN-8952-3
Ubuntu26.10python-tornado6.5.5-5ubuntu1.3UBUNTU-CVE-2026-103263 USN-8952-1 USN-8952-2 USN-8952-3
UbuntuPro:16.04:LTSpython-tornado4.2.1-1ubuntu3.1+esm6UBUNTU-CVE-2026-103263 USN-8952-1 USN-8952-2 USN-8952-3
UbuntuPro:18.04:LTSpython-tornado4.5.3-1ubuntu0.2+esm6UBUNTU-CVE-2026-103263 USN-8952-1 USN-8952-2 USN-8952-3
UbuntuPro:20.04:LTSpython-tornado6.0.3+really5.1.1-3ubuntu0.1~esm7USN-8952-1
UbuntuPro:20.04:LTSpython-tornado6.0.3+really5.1.1-3ubuntu0.1~esm8USN-8952-2
UbuntuPro:20.04:LTSpython-tornado6.0.3+really5.1.1-3ubuntu0.1~esm9USN-8952-3
UbuntuPro:22.04:LTSpython-tornado6.1.0-3ubuntu0.1~esm8UBUNTU-CVE-2026-103263 USN-8952-1 USN-8952-2 USN-8952-3
SUSELinux 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 morepython-tornado66.3.2-150400.9.32.1SUSE-SU-2026:5254-1
Azure Linux3python-tornadono fix listedAZL-105375
Alpaquita25, streampy3-tornado6.5.10-r0BELL-CVE-2026-103263

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

Red Hat rates this Moderate.

Red Hat's statement

A moderate information-disclosure vulnerability was found in Tornado's StaticFileHandler. Tornado is shipped or depended upon in Red Hat Enterprise Linux (for example the pcs component), Red Hat OpenShift Container Platform, and other Red Hat products that bundle the python-tornado package or pull it in through components such as python-flit and python-pep517. StaticFileHandler resolves requested paths using os.path.abspath() and a string prefix check against the configured static root without resolving symbolic links, while the subsequent file access does follow them. As a result, an unauthenticated remote attacker can request a path that resolves to a symbolic link located inside the static root but pointing outside it and read arbitrary files readable by the server process user, such as configuration files, private keys, and application credentials; no integrity or availability impact is possible. Exploitation requires that a symbolic link pointing outside the static root already exists (or can be created) inside the static directory, for example through build or deployment tooling or user uploads. For this reason Red Hat rates this flaw MODERATE with CVSS:3.1 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), while the upstream CVSS:4.0 score of 8.2 treats the presence of such a link as only a preparatory requirement. Red Hat products whose affected components are resolved as DEFER will not receive a fix at this time because the impact is moderate and the CVSS score is below 7.0; the residual risk is unauthenticated disclosure of files readable by the process user when a symlink pointing outside the static root is present in the served static directory. For community streams such as Fedora and EPEL, a fix is being pursued through the upstream community. Affected Red Hat OpenStack Platform 16.2 components are out of support scope.

Red Hat's mitigation

Upgrade to tornado 6.5.9 or later; as a workaround, avoid symlinks inside static roots served by StaticFileHandler and do not point static roots at directories writable by untrusted processes or mount targets (Docker volumes, npm link).

ProductPackageStateAdvisory
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Fix deferred
Lightspeed Corelightspeed-core/rag-tool-cpu-rhel9Fix deferred
Lightspeed Corelightspeed-core/rag-tool-cuda-12.9-rhel9Fix deferred
Migration Toolkit for Applications 8mta/mta-solution-server-rhel9Out of support scope
OpenShift Lightspeedopenshift-lightspeed/lightspeed-ocp-rag-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/lightspeed-chatbot-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/lightspeed-chatbot-rhel9Fix deferred
Red Hat Enterprise Linux 10python-tornadoAffected
Red Hat Enterprise Linux 10rhel10/keylime-registrarFix deferred
Red Hat Enterprise Linux 10rhel10/keylime-verifierFix deferred
Red Hat Enterprise Linux 8pcsFix deferred
Red Hat Enterprise Linux 9python-tornadoAffected
Red Hat Enterprise Linux 9rhel9/keylime-registrarFix deferred
Red Hat Enterprise Linux 9rhel9/keylime-verifierFix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gaudi-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-rocm-rhel9Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/disk-image-cuda-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-llama-stack-core-rhel9Fix 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-103263.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON