Rust advisories / crate
Security history · hyper · data from Oct 24, 2026
Is hyper safe to use? Its security history
VerdictNo open advisories. 6 past vulnerabilities were fixed; use 0.14.12 or newer to be clear of all of them.
Every advisory, newest first
- UnsoundRUSTSEC-2022-0022 · 2022-05-10Parser creates invalid uninitialized value
- Vulnerability MediumRUSTSEC-2021-0078 · 2021-07-07Lenient `hyper` header parsing of `Content-Length` could allow request smuggling
- Vulnerability CriticalRUSTSEC-2021-0079 · 2021-07-07Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss
- Vulnerability HighRUSTSEC-2021-0020 · 2021-02-05Multiple Transfer-Encoding headers misinterprets request payload
- Vulnerability CriticalRUSTSEC-2020-0008 · 2020-03-19Flaw in hyper allows request smuggling by sending a body in GET requests
- Vulnerability MediumRUSTSEC-2017-0002 · 2017-01-23headers containing newline characters can split messages
- Vulnerability MediumRUSTSEC-2016-0002 · 2016-05-09HTTPS MitM vulnerability due to lack of hostname verification
Check your version
Run cargo tree -i hyper to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
Download trends, dependents and alternatives: hyper crate data.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Before you depend on ithyper crate dataReal downloads, dependents and alternatives.Read it next →Did this answer your question?