CVE-2025-2886: Terminating targets role delegations are not respected in tough
Summary
Delegations are a mechanism defined by the TUF specification that allow multiple different identities to provide and sign content within a single repository. Terminating delegations and delegation priority give a TUF repository unambiguous control over how overlapping delegations are resolved. tough erroneously will not terminate a search as required, and will accept information from a lower-priority delegation that should have been ignored.
Impact
When interacting with TUF repositories that use delegations, the tough client could fetch targets owned by the incorrect role. An actor which had delegated ownership of a subset of a TUF repository could provide arbitrary contents to tough clients for targets owned by the delegating identity.
Impacted versions: < v0.20.0
Patches
A fix for this issue is available in tough version 0.20.0 and later. Customers are advised to upgrade to version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.
Workarounds
There is no recommended work around. Customers are advised to upgrade to version 0.20.0 or the latest version.
References
If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting
Acknowledgement
These issues were identified by the TUF-Conformance project. We would like to thank Google for collaborating on this issue through the coordinated vulnerability disclosure process.
Other sources
Missing validation of terminating delegation causes the client to continue searching the defined delegation list, even after searching a terminating delegation. 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.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-2886?
CVE-2025-2886 is classified as a moderate severity vulnerability.
How do I fix CVE-2025-2886?
To fix CVE-2025-2886, upgrade the Tough software to version 0.20.0 or later.
What type of vulnerability is CVE-2025-2886?
CVE-2025-2886 is a vulnerability related to missing validation of terminating delegations.
What can happen if CVE-2025-2886 is exploited?
Exploitation of CVE-2025-2886 could lead to the client fetching a target from an incorrect source, resulting in altered target contents.
Which versions of Tough are affected by CVE-2025-2886?
CVE-2025-2886 affects versions of Tough prior to 0.20.0.