Is tough affected by CVE-2025-2888?

crates.io tough is affected in <0.20.0.

Is CVE-2025-2888 being exploited?

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

medium

CVE-2025-2888

Q: Is CVE-2025-2888 being exploited?

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

crates.io · tough

Summary

tough timestamp metadata is cached when it fails snapshot rollback check

Severity: medium
EPSS: 0.3% (p20)
Also known as: GHSA-76g3-38jv-wxh4
Published: 2025-03-28

References

https://github.com/awslabs/tough/security/advisories/GHSA-76g3-38jv-wxh4
https://nvd.nist.gov/vuln/detail/CVE-2025-2888
https://github.com/awslabs/tough/commit/9b400e1c8b7d6b9ab8009104fa7fe5884db05f18

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-2020-15093 — high · crates.io/tough
CVE-2025-2886 — medium · crates.io/tough
CVE-2025-2885 — 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.