Is tough affected by CVE-2020-15093?

crates.io tough is affected in <0.7.1.

Is CVE-2020-15093 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 1.4%.

high

CVE-2020-15093

Q: Is CVE-2020-15093 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 1.4%.

crates.io · tough

Summary

Improper verification of signature threshold in tough

Severity: high
EPSS: 1.4% (p68)
Also known as: GHSA-5q2r-92f9-4m49, RUSTSEC-2020-0024
Published: 2021-08-25

References

https://github.com/awslabs/tough/security/advisories/GHSA-5q2r-92f9-4m49
https://nvd.nist.gov/vuln/detail/CVE-2020-15093
https://github.com/theupdateframework/tuf/pull/974

Related advisories

CVE-2026-6967 — high · crates.io/tough
CVE-2026-6966 — high · crates.io/tough
CVE-2021-41150 — high · crates.io/tough
CVE-2021-41149 — high · crates.io/tough
CVE-2025-2886 — medium · crates.io/tough
CVE-2025-2885 — medium · crates.io/tough
CVE-2025-2888 — medium · crates.io/tough
CVE-2025-2887 — medium · crates.io/tough

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.