# CVE-2025-2887: Failure to detect delegated target rollback in tough

> Attackers can alter target contents by exploiting a failure to detect delegated target rollbacks in the tough library.

- **Severity:** Medium 5.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Mar 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-q6r9-r9pw-4cf7

## What is CVE-2025-2887?

CVE-2025-2887 is a medium-severity vulnerability in AWS tough, published on 27 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

During a target rollback, the client fails to detect the rollback for delegated targets. This could cause the client to fetch a target from an incorrect source, altering the target contents. 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.

Weakness: CWE-1025 (Comparison Using Wrong Factors)

## Which versions are affected by CVE-2025-2887?

2 open source packages ship an affected version, including tough. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tough` | crates.io | All versions | 0.20.0 |
| `tough` | crates.io | All versions | 0.20.0 |

Products: Amazon Tough.

## How do I fix CVE-2025-2887?

Upgrade tough to 0.20.0 or later.

## Is CVE-2025-2887 being exploited?

There is no known exploitation of CVE-2025-2887 in the wild and no public exploit code.

## Other vulnerabilities in AWS tough

- [CVE-2020-15093](https://insights.sbomify.com/CVE-2020-15093/): Improper verification of signature threshold in tough (high 8.6)
- [CVE-2021-41149](https://insights.sbomify.com/CVE-2021-41149/): Improper sanitization of target names in tough (high 8.2)
- [CVE-2021-41150](https://insights.sbomify.com/CVE-2021-41150/): Improper sanitization of delegated role names in tough (high 8.2)
- [CVE-2026-6967](https://insights.sbomify.com/CVE-2026-6967/): Missing Delegated Metadata Validation in awslabs/tough (high 7.1)
- [CVE-2026-6968](https://insights.sbomify.com/CVE-2026-6968/): Multiple Path Traversal Variants in awslabs/tough (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2887 and fix it if it is affected.

What it is: CVE-2025-2887 is a medium-severity vulnerability in AWS tough, published on 27 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-2887 in the wild and no public exploit code.

Affected packages and fixed versions:
- tough (crates.io): affected all versions; fixed in 0.20.0
- tough (crates.io): affected all versions; fixed in 0.20.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2887/ (Markdown: https://insights.sbomify.com/CVE-2025-2887/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2887
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2887
- OSV: https://osv.dev/vulnerability/CVE-2025-2887

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2887/
Summaries are generated and may contain mistakes; the official description above is the record.