Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The tough crate before 0.22.0 and the tuftool crate before 0.15.0 do not check that signatures used to meet a delegated role's threshold come from unique keys. An attacker who already holds a valid signing key can duplicate one signature to reach the threshold, so clients may accept forged delegated role metadata. Upgrade tough to 0.22.0 and tuftool to 0.15.0; no workarounds are known.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.0 | High | 4.0 | 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 | CNA (AMZN) |
- CISA KEV Not listed.
- EPSS 0.0028, the 21st percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:17 UTC First seen by agentprime
- 31 Oct 2026, 15:17 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8m7c-8m39-rv4x
- OSV: GHSA-8m7c-8m39-rv4x
- github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x
- nvd.nist.gov/vuln/detail/CVE-2026-6966
- aws.amazon.com/security/security-bulletins/2026-019-aws
- crates.io/crates/tough/0.22.0
- crates.io/crates/tuftool/0.15.0
- github.com/awslabs/tough
- github.com/awslabs/tough/releases/tag/tough-v0.22.0
- github.com/awslabs/tough/releases/tag/tuftool-v0.15.0