PatchTheCVEtough vulnerabilities and fixes
Recent CVEs affecting tough, with upgrade or downgrade steps. 3 tracked.
tough has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-04-24. Highest priority: CVE-2026-6968 (score 37/100).
- CVE-2026-6968 MEDIUM 5.9 UPGRADE UPGRADE Incomplete path traversal fixes in awslabs/tough before tough-v0.22.0 allow remote authenticated users with de
- CVE-2026-6967 MEDIUM 5.9 UPGRADE UPGRADE Missing expiration, hash, and length enforcement in delegated metadata validation in awslabs/tough before toug
- CVE-2026-6966 MEDIUM 5.3 UPGRADE UPGRADE Improper verification of cryptographic signature uniqueness in delegated role validation in awslabs/tough befo
FAQ
How do I fix tough vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is tough being exploited right now?
None of the tracked tough CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which tough CVE should I patch first?
CVE-2026-6968 currently ranks highest (37/100): Incomplete path traversal fixes in awslabs/tough before tough-v0.22.0 allow remote authenticated users with de.