AWS Tough CVE-2026-6966

| EUVD-2026-25627 HIGH
Improper Verification of Cryptographic Signature (CWE-347)
2026-04-24 AMZN
7.0
CVSS 4.0
Share

CVSS VectorNVD

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/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
Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

4
Re-analysis Queued
Apr 24, 2026 - 21:22 vuln.today
cvss_changed
Analysis Generated
Apr 24, 2026 - 20:32 vuln.today
Severity Changed
Apr 24, 2026 - 20:22 NVD
MEDIUM HIGH
CVSS changed
Apr 24, 2026 - 20:22 NVD
5.3 (MEDIUM) 7.0 (HIGH)

DescriptionNVD

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.

AnalysisAI

Signature duplication in AWS Tough TUF client prior to v0.22.0 allows authenticated attackers to bypass threshold signature requirements for delegated role metadata by reusing a single valid signature multiple times. The flaw undermines TUF's multi-signature integrity model, enabling acceptance of forged metadata with reduced cryptographic validation. …

Sign in for full analysis, threat intelligence, and remediation guidance.

RemediationAI

Within 24 hours: Inventory all systems and applications using AWS Tough TUF client and identify current versions in use. Within 7 days: Upgrade Tough TUF client to v0.22.0 or later and tuftool to v0.15.0 or later across all environments; test metadata validation workflows post-upgrade. …

Sign in for detailed remediation steps.

Share

CVE-2026-6966 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy