Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The tough package (crates.io), versions before 0.7.1, does not check that the keys behind provided signatures are unique when counting toward a signature threshold. An attacker who holds one valid signing key can produce several signatures from it, which can satisfy a threshold that requires multiple distinct keys and make metadata appear valid. Upgrade to tough 0.7.1 or later.
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 |
|---|---|---|---|---|
| 8.6 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.014, the 72nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:24 UTC First seen by agentprime
- 31 Oct 2026, 14:24 UTC Confirmed by OSV