Cyber Resilience

CVE-2025-2888

Amazon Tough ≤ 0.20.0

Published
27 March 2025
Modified
14 October 2025
Patch / advisory
View advisory
CVSS Score v4 5.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0031 23th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-2888 is a medium-severity Comparison Using Wrong Factors (CWE-1025) vulnerability in Amazon Tough. Its CVSS base score is 5.7 (Medium).

Operationally, ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

During a snapshot rollback, the client incorrectly caches the timestamp metadata. If the client checks the cache when attempting to perform the next update, the update timestamp validation will fail, preventing the next update until the cache is cleared. Users…

more

should upgrade to tough version 0.20.0 or later and ensure any forked or derivative code is patched to incorporate the new fixes.

CWE(s)
CWE-1025

Related Threats

CVEs Like This One

CVE-2025-2887Same product: Amazon Tough
CVE-2025-2886Same product: Amazon Tough
CVE-2025-2885Same product: Amazon Tough
CVE-2026-6966Same product: Amazon Tough
CVE-2026-6968Same product: Amazon Tough
CVE-2026-6967Same product: Amazon Tough
CVE-2024-28115Same vendor: Amazon
CVE-2026-1386Same vendor: Amazon
CVE-2023-36467Same vendor: Amazon
CVE-2026-6437Same vendor: Amazon

Affected Assets

amazon
tough
≤ 0.20.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover incorrect comparison logic after implementation but does not stop the flaw from being written.

SA-15 Development Process, Standards, and Tools partial match

Requiring a documented development process and tools can embed standards that reduce introduction of erroneous comparison factors.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC activities such as code review and logic testing directly prevent incorrect comparison factors in code.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect incorrect comparison results during development and acceptance.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes requirements and reviews that can catch incorrect comparison logic.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify correct comparison criteria and validation rules.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper comparison logic and factor selection.

References