awslabs/tough Delegated Roles Signature Threshold Bypass

The awslabs/tough library, a component used in securing software update systems via The Update Framework (TUF), is susceptible to a signature bypass vulnerability in versions prior to 0.22.0. This flaw stems from inadequate validation of cryptographic signature uniqueness during delegated role validation. An attacker with access to a valid signing key can exploit this by creating multiple valid signatures, circumventing the intended threshold of unique keys required for metadata validation. This issue was publicly disclosed on May 5, 2026, and affects systems relying on vulnerable versions of tough and tuftool. Successful exploitation allows an attacker to inject forged delegated role metadata, potentially compromising the integrity of software updates.

Attack Chain

1. Attacker gains access to a valid signing key used within the TUF repository.
2. Attacker crafts malicious delegated role metadata.
3. Attacker generates multiple valid signatures for the crafted metadata using the compromised key, effectively duplicating the signature.
4. Attacker uploads the malicious metadata with the duplicated signatures to the repository.
5. A TUF client attempts to update its metadata.
6. The client fetches the attacker-controlled delegated role metadata.
7. Due to the lack of signature uniqueness validation in vulnerable tough versions, the client incorrectly validates the metadata as legitimate, satisfying the signature threshold requirement with duplicated signatures.
8. The client trusts the forged delegated role metadata, potentially leading to the installation of malicious software or other unauthorized actions.

Impact

Successful exploitation of this vulnerability allows an attacker to compromise the integrity of software updates. By bypassing the intended signature threshold, the attacker can inject malicious metadata that the client trusts, potentially leading to the installation of compromised software. This could affect any system relying on awslabs/tough for secure software updates, potentially impacting a large number of users and systems depending on the affected repository.

Recommendation

• Upgrade rust/tough to version 0.22.0 or later to address the signature uniqueness validation flaw.
• Upgrade rust/tuftool to version 0.15.0 or later to incorporate the necessary fixes.
• Implement monitoring for unexpected or duplicated signatures in TUF metadata updates, leveraging the Detect Tough Metadata Signature Duplication Sigma rule.
• Monitor for network connections originating from processes associated with TUF metadata updates to unusual or suspicious domains, triggering on anomalous activity with the Detect Tough Metadata Update Network Activity Sigma rule.