CVE-2025-2888: tough timestamp metadata is cached when it fails snapshot rollback check

CVE-2025-2888 · Severity: low · CVSS 3.1 · Published 2025-03-28

tough timestamp metadata is cached when it fails snapshot rollback check

Technologies: tough (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2025-2888 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-2888 being exploited in the wild.
How severe is CVE-2025-2888?
Low severity, with a CVSS score of 3.1, published 28 March 2025.
Which products and versions are affected?
tough (crates.io) SEMVER:introduced=0,fixed=0.20.0.
Is there a fix for CVE-2025-2888?
Yes. tough (crates.io): upgrade to 0.20.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-2888?
Check whether you run tough (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • tough (crates.io): upgrade to 0.20.0 or later
    cargo update -p tough

Affected products

  • tough (crates.io) SEMVER:introduced=0,fixed=0.20.0

Identifiers

  • CVE-2025-2888
  • GHSA-76g3-38jv-wxh4

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.