tokio (cargo) has 7 known vulnerabilities, the worst rated HIGH. No single fixed version is recorded that clears every advisory, so check each one below. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
0 packages depend on it
dependents not yet indexed for this ecosystem
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so cargo packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 70th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-fg7r-2g4j-5cgr, the advisory selected below
If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called…
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CyberXYZ does not call a package safe in absolute terms. It records 7 known vulnerabilities for tokio (cargo), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 7 known vulnerabilities for tokio (cargo), the worst rated HIGH. These include GHSA-fg7r-2g4j-5cgr, GHSA-5wjr-9356-4wc8, GHSA-7rrj-xr53-82p7, GHSA-2grh-hm3w-w7hv, GHSA-rr8g-9fpq-6wmg.
Search tokio in CyberXYZ Check at https://cyberxyz.io/check?q=tokio. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 09:37 UTC. The most recent advisory here was published 2026-10-23. Updated continuously from NVD, GHSA, OSV and CNA feeds.