Rust advisories / crate
Security history · futures-task · data from Oct 24, 2026
Is futures-task safe to use? Its security history
VerdictNo open advisories. 2 past vulnerabilities were fixed; use 0.3.6 or newer to be clear of all of them.
2advisories on record
2vulnerabilities
0unmaintained notices
0.3.6newest fixed version
Every advisory, newest first
- Vulnerability HighRUSTSEC-2020-0060 · 2020-09-04futures_task::waker may cause a use-after-free if used on a type that isn't 'static
- Vulnerability MediumRUSTSEC-2020-0061 · 2020-05-03futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer
Check your version
Run cargo tree -i futures-task 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: futures-task 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 itfutures-task crate dataReal downloads, dependents and alternatives.Read it next →Did this answer your question?