Improper verification of cryptographic signature uniqueness in delegated role validation in awslabs/tough before tough-v0.22.0 allows remote authenticated users to byp…

Code

The project this record applies to. Exploit listings stay in References.

• Repository · github.com

Timeline

Detection, updates, and resolution for this record.

1. Apr 24, 2026 · NIST NVD

   Detected

   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.

2. Jun 17, 2026 · NIST NVD

   Updated

   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.

Affected

• cpe amazon/toughversion unspecified
• cpe amazon/tuftoolversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-6966

  Official CVE identifier

  cve.org
• NIST NVDVulnerability recordCVE-2026-6966

  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

  nvd.nist.gov

References

• Vendor Advisory · aws.amazon.com
• Product · crates.io
• Product · crates.io
• Release Notes · github.com
• Release Notes · github.com
• Vendor Advisory · github.com