Description
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.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 12 SP1 | python-backports.ssl_match_hostname | 3.4.0.2-15.1 | SUSE-SU-2016:1195-1 |
| SLES 12 SP1 | python-tornado | 4.2.1-11.1 | SUSE-SU-2016:1195-1 |
| SLES 12 | python-backports.ssl_match_hostname | 3.4.0.2-15.1 | SUSE-SU-2016:1195-1 |
| SLES 12 | python-tornado | 4.2.1-11.1 | SUSE-SU-2016:1195-1 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | tornado | < 3.2.2 | 3.2.2 | GHSA-8vpw-mgpf-mpvv |
Advisories 3
- DLA-475-1 python-tornado - security update Debian Security (DSA / DLA) · Mar 9, 2026
- DLA-279-1 python-tornado - security update Debian Security (DSA / DLA) · Mar 9, 2026
- SUSE-SU-2016:1195-1 Security update for python-tornado SUSE / openSUSE Security Updates · Feb 4, 2026