Tornado vulnerable to Header Injection and XSS via reason argument
Published 20 Jul 2026 · Updated 20 Jul 2026
Is your project on an affected tornado?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <6.5.3
- Fixed in
- 6.5.3
pip install 'tornado>=6.5.3'Details
Header injection and XSS via reason argument
Summary
The reason argument (used by both RequestHandler.set_status and tornado.web.HTTPError is designed to allow applications to pass custom "reason" phrases (the "Not Found" in HTTP/1.1 404 Not Found) to the HTTP status line (mainly for non-standard status codes). Vulnerabilities exist in Tornado versions prior to 6.5.3 if untrusted data is passed as the reason argument.
Details
In vulnerable versions, the supplied reason phrase is used unescaped in HTTP headers (where it could be used for header injection) or in HTML in the default error page (where it could be used for XSS).
Impact
- Type: Reflected Cross-Site Scripting (CWE-79) in default error page, or header injection (CWE-644)
- Actors: Remote attacker who can cause the application to raise
HTTPError/set_statuswith an attacker-controlledreason(e.g., via query parameter used by developer). - Effect: Execution of arbitrary JavaScript in victims' browsers when they view the error page — possible session token theft, CSRF escalation, UI spoofing, or other client-side attacks depending on context.
- Scope: Only applications that explicitly reflect untrusted input into
reasonare affected.
Mitigation
Aside from upgrading to Tornado 6.5.3 or newer, the vulnerability can be mitigated by not using untrusted data for the reason argument. In the intended use case the reason argument would generally be a string literal and not derived from user input. Also, the reason argument is rarely required (reason phrases are not used at all in HTTP/2) and can generally be omitted.
For a general-purpose error message in HTTPError, consider using the log_message argument instead of reason.
Is GHSA-pr2v-jx2c-wg9f in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected tornado, and gives you the command that fixes it.
More advisories for tornado
- LowCVE-2026-126347Tornado: Open redirect via triple-slash redirect paths · 13 Nov 2026
- MediumCVE-2026-115927Tornado: Event loop blocking and excess memory use from chunked bodies with many small chunks · 28 Oct 2026
- LowCVE-2026-116578Tornado: Open redirect in RedirectHandler via protocol-relative URLs · 28 Oct 2026
- MediumCVE-2026-116577Tornado: Quadratic CPU usage when parsing HTTP headers with line folding · 28 Oct 2026
- MediumCVE-2026-103261Tornado: Unbounded query-string argument count allows event-loop-stalling DoS · 30 Sept 2026
- HighCVE-2026-103262tornado: CurlAsyncHTTPClient enforces no response-size limit — decompression bomb drives unbounded memory accumulation to OOM · 30 Sept 2026
References
- Linkgithub.com/tornadoweb/tornado/security/advisories/GHSA-pr2v-jx2c-wg9f
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-67724
- Linkgithub.com/tornadoweb/tornado/commit/9c163aebeaad9e6e7d28bac1f33580eb00b0e421
- Linkgithub.com/pypa/advisory-database/tree/main/vulns/tornado/PYSEC-2025-265.yaml
- Packagegithub.com/tornadoweb/tornado
- Linkgithub.com/tornadoweb/tornado/releases/tag/v6.5.3
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.