Improper verification of cryptographic signature uniqueness in delegated role validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users to bypass the TUF signature threshold requirement by duplicating a valid signature, causing the client to accept forged delegated role metadata. We recommend you upgrade to tough-v0.22.0 / tuftool-v0.15.0.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://aws.amazon.com/security/security-bulletins/2026-019-aws/ Vendor Advisory
- https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.0 · amazonNVD modified 2026-10-20 19:17
Affected (CPE criteria) 2
cpe:2.3:a:amazon:tough:*:*:*:*:*:rust:*:*cpe:2.3:a:amazon:tuftool:*:*:*:*:*:rust:*:*
References 6
- https://aws.amazon.com/security/security-bulletins/2026-019-aws/ Vendor Advisory
- https://crates.io/crates/tough/0.22.0 Product
- https://crates.io/crates/tuftool/0.15.0 Product
- https://github.com/awslabs/tough/releases/tag/tough-v0.22.0 Release Notes
- https://github.com/awslabs/tough/releases/tag/tuftool-v0.15.0 Release Notes
- https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x Vendor Advisory