Vulnerability CriticalRUSTSEC-2021-0079 · hyper
RUSTSEC-2021-0079: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss
Short answerA security vulnerability in the hyper crate: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss. Critical severity (CVSS 9.1). Fixed in 0.14.10: update to a fixed version.
| Crate | hyper |
|---|---|
| Type | Vulnerability |
| Affected versions | Before 0.14.10. |
| Fixed in | 0.14.10 |
| Severity | Critical, CVSS 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| Published | 2021-07-07 |
| Last changed | 2026-10-12 |
| Also known as | CVE-2021-32714, GHSA-5h46-h7hh-c6x9 |
What to do
- See which version you have:
cargo tree -i hyper(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p hyper. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplehyper = "0.14.10") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
When decoding chunk sizes that are too large, hyper's code would encounter an integer overflow. Depending on the situation, this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.
To be vulnerable, you must be using hyper for any HTTP/1 purpose, including as a client or server, and consumers must send requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible, any upstream proxies must accept a chunk size greater than 64 bits.
References
- Package: crates.io/crates/hyper
- Advisory: rustsec.org/advisories/RUSTSEC-2021-0079.html
- Web: github.com/hyperium/hyper/commit/efd9a9821fd2f1ae04b545094de76a435b62e70f
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for hyper
- Vulnerability MediumRUSTSEC-2016-0002 · 2016-05-09HTTPS MitM vulnerability due to lack of hostname verification
- Vulnerability MediumRUSTSEC-2017-0002 · 2017-01-23headers containing newline characters can split messages
- Vulnerability CriticalRUSTSEC-2020-0008 · 2020-03-19Flaw in hyper allows request smuggling by sending a body in GET requests
- Vulnerability HighRUSTSEC-2021-0020 · 2021-02-05Multiple Transfer-Encoding headers misinterprets request payload
- Vulnerability MediumRUSTSEC-2021-0078 · 2021-07-07Lenient `hyper` header parsing of `Content-Length` could allow request smuggling
- UnsoundRUSTSEC-2022-0022 · 2022-05-10Parser creates invalid uninitialized value
Up next
Same cratehyper: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?