Tough vulnerabilitiesRanked by how likely they are to be used.
Tough is made by Amazon. We track 7 published vulnerabilities in it, across 31 versions. None of them is on the list of flaws known to be exploited today. If you run Tough, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Tough vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Tough's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Tough flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.4%CVE-2020-15093High
The tough library (Rust/crates.io) prior to version 0.7.1 does not properly verify the threshold of cryptographic signatures.
- 1.3%CVE-2021-41150Medium
Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories.
- 1.1%CVE-2021-41149High
Tough provides a set of Rust libraries and tools for using and generating the update framework (TUF) repositories.
- 0.3%CVE-2025-2888Medium
During a snapshot rollback, the client incorrectly caches the timestamp metadata.
- 0.3%CVE-2025-2885Medium
Missing validation of the root metatdata version number could allow an actor to supply an arbitrary version number to the client instead of the intended version in the root metadata file, altering the version fetched...
- 0.3%CVE-2025-2886Medium
Missing validation of terminating delegation causes the client to continue searching the defined delegation list, even after searching a terminating delegation.
- 0.3%CVE-2025-2887Medium
During a target rollback, the client fails to detect the rollback for delegated targets.
Running Tough? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The tough library (Rust/crates.io) prior to version 0.7.1 does not properly verify the threshold of cryptographic signatures. It allows an attacker to duplicate a valid signature in order to circumvent TUF requiring a minimum threshold of unique signatures before the metadata is considered valid. A fix is available in version 0.7.1. CVE-2020-6174 is assigned to the same vulnerability in the TUF reference implementation.
- Matched to
- Tough on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 7 published vulnerabilities listed under the name Tough, across 31 versions.
None of Tough's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Tough. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.