Cyber Resilience

CVE-2025-2886

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-2886 is a medium-severity Always-Incorrect Control Flow Implementation (CWE-670) 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

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…

more

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-670

Related Threats

CVEs Like This One

CVE-2025-2888Same product: Amazon Tough
CVE-2025-2885Same product: Amazon Tough
CVE-2025-2887Same 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

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V9.2.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation at post-design stages directly exercises control-flow paths and reveals mismatches between implemented and intended behavior.

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

Requiring a documented development process and supporting tools reduces the chance that incorrect control-flow logic is introduced in the first place.

SI-2 Flaw Remediation partial match

Flaw identification and remediation processes can locate and correct control-flow errors once they manifest as incorrect runtime behavior.

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 practices directly prevent incorrect control-flow implementations via reviews, testing, and static analysis.

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 in development and acceptance can detect paths that deviate from intended logic.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle processes can catch incorrect control-flow logic during design and code review.

A.8.28 Secure coding partial match
prevents

Secure coding standards and reviews directly target flawed control-flow implementations.

A.8.32 Change management partial match
prevents

Change-management gates may prevent deployment of flawed logic but do not address the coding defect itself.

References