Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The tough crate (crates.io) versions 0.9.0 through 0.21.x and the tuftool crate through 0.14.x are affected. An attacker holding delegated signing authority on a TUF repository, which is a remote authenticated role, can serve expired or otherwise invalid delegated targets metadata that tough accepts, because delegated metadata is missing expiration, hash, and length checks. 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.1 | 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:L | CNA (AMZN) |
- CISA KEV Not listed.
- EPSS 0.0025, the 16th percentile, on 9 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-4v58-8p28-2rq3
- OSV: GHSA-4v58-8p28-2rq3
- github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3
- nvd.nist.gov/vuln/detail/CVE-2026-6967
- 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