Rust advisories / crate
Security history · tokio · data from Oct 24, 2026
Is tokio safe to use? Its security history
VerdictNo open advisories. 4 past vulnerabilities were fixed; use 1.54.1 or newer to be clear of all of them.
7advisories on record
4vulnerabilities
0unmaintained notices
1.54.1newest fixed version
Every advisory, newest first
- VulnerabilityRUSTSEC-2026-0384 · 2026-10-21Race condition in `tokio::time::Interval` on Tokio v1.54.0
- UnsoundRUSTSEC-2026-0386 · 2026-10-13`AsyncFd::new` and related constructors violate I/O safety
- UnsoundRUSTSEC-2025-0023 · 2025-04-07Broadcast channel calls clone in parallel, but does not require `Sync`
- UnsoundRUSTSEC-2023-0005 · 2023-01-11`tokio::io::ReadHalf<T>::unsplit` is Unsound
- VulnerabilityRUSTSEC-2023-0001 · 2023-01-04reject_remote_clients Configuration corruption
- VulnerabilityRUSTSEC-2021-0124 · 2021-11-16Data race when sending and receiving after closing a `oneshot` channel
- VulnerabilityRUSTSEC-2021-0072 · 2021-07-07Task dropped in wrong thread when aborting `LocalSet` task
Check your version
Run cargo tree -i tokio 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: tokio 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 ittokio crate dataReal downloads, dependents and alternatives.Read it next →Did this answer your question?