tough (cargo) has 10 known vulnerabilities, the worst rated HIGH. Upgrade to 0.22.0 or later to clear all of them. No malicious-package signal is recorded.
Improper verification of cryptographic signature uniqueness in delegated role validation in awslabs/tough before tough-v0.22.0 allows remote authenticated…
CyberXYZ does not call a package safe in absolute terms. It records 10 known vulnerabilities for tough (cargo), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does tough have known vulnerabilities?
Yes. CyberXYZ records 10 known vulnerabilities for tough (cargo), the worst rated HIGH. These include GHSA-8m7c-8m39-rv4x, GHSA-4v58-8p28-2rq3, GHSA-x3r5-q6mj-m485, GHSA-r56q-vv3c-6g9c, GHSA-5q2r-92f9-4m49.
Which version of tough should I use?
0.22.0 or later clears every advisory recorded for tough (cargo). Check the release you pick before installing it.
How do I check tough before installing?
Search tough in CyberXYZ Check at https://cyberxyz.io/check?q=tough. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:31 UTC. The most recent advisory here was published 2026-05-05. Updated continuously from NVD, GHSA, OSV and CNA feeds.