Tornado before 3.2.2 sends arbitrary responses that contain a fixed CSRF token and may be sent with HTTP compression, which makes it easier
Tornado before 3.2.2 sends arbitrary responses that contain a fixed CSRF token and may be sent with HTTP compression, which makes it easier for remote attackers to conduct a BREACH attack and determine this token via a series of crafted requests.
- Published
- Jan 24, 2020
- Updated
- Jun 16, 2026
- EPSS
- 2.5% · 84th percentile
- CWE
- CWE-203
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| tornadoweb | tornado | cpe:2.3:a:tornadoweb:tornado |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tornadoweb tornadobefore 3.2.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | python-tornado | before 3.2.2-1 | 3.2.2-1 |
| Debian:6.0 | python-tornado | before 1.0.1-1+deb6u1 | 1.0.1-1+deb6u1 |
| Debian:7 | python-tornado | before 2.3-2+deb7u1 | 2.3-2+deb7u1 |
| PyPI | tornado | before 3.2.2 | 3.2.2 |
| SUSE:Linux Enterprise Desktop 12 | python-backports.ssl_match_hostname | before 3.4.0.2-15.1 | 3.4.0.2-15.1 |
| SUSE:Linux Enterprise Desktop 12 | python-tornado | before 4.2.1-11.1 | 4.2.1-11.1 |
Same product
tornadoweb: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-14029Tornado before 6.4.1 HTTP Request Smuggling via Transfer-Encoding36Monitor
- CVE-2023-54397Tornado before 6.3.3 HTTP Request Smuggling via Content-Length36Monitor
- CVE-2026-91990Tornado before 6.5.8 Memory Amplification DoS via multipart34Monitor
- CVE-2026-31958Tornado has a DoS due to too many multipart parts34Monitor
- CVE-2026-91992Tornado before 6.5.7 Credential Leak via Handle Reuse32Monitor
- CVE-2026-82397Tornado: Urlencoded body parsing omits max_num_fields, so one request can stall the event loop30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:python-tornado | 3.2.2-1 · Debian:12 | Package registry (OSV) |
| PyPI:tornado | 3.2.2 | Package registry (OSV) |
| suse:python-backports.ssl_match_hostname | 3.4.0.2-15.1 · SUSE:Linux Enterprise Desktop 12 | Package registry (OSV) |
| suse:python-tornado | 4.2.1-11.1 · SUSE:Linux Enterprise Desktop 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- openwall.com/lists/oss-security/2015/05/19/4
- www.tornadoweb.org/en/stable/releases/v3.2.2.html
- bugzilla.novell.com/show_bug.cgi?id=930362
- bugzilla.redhat.com/show_bug.cgi?id=1222816
- github.com/tornadoweb/tornado/commit/1c36307463b1e8affae100bf9386948e6c1b2308
Vendor advisories and official records. Exploit/PoC links are deliberately left out.