Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The Python tuf package, versions before 0.12.0, will trust a previously downloaded root metadata file that failed verification at download time. An attacker who can intercept and serve several successive new root metadata versions, such as through a man-in-the-middle attack, can end with an improperly signed version that then controls the trust chain for future updates. Upgrade to tuf 0.12.0 or newer; 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 |
|---|---|---|---|---|
| 8.7 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0067, the 52nd percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:38 UTC First seen by agentprime
- 31 Oct 2026, 14:38 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-f8mr-jv2c-v8mg
- OSV: GHSA-f8mr-jv2c-v8mg
- github.com/theupdateframework/tuf/security/advisories/GHSA-f8mr-jv2c-v8mg
- nvd.nist.gov/vuln/detail/CVE-2020-15163
- github.com/theupdateframework/tuf/pull/885
- github.com/theupdateframework/tuf/commit/3d342e648fbacdf43a13d7ba8886aaaf07334af7
- github.com/pypa/advisory-database/tree/main/vulns/tuf/PYSEC-2020-145.yaml
- github.com/theupdateframework/tuf
- github.com/theupdateframework/tuf/releases/tag/v0.12.0
- pypi.org/project/tuf