Advisory record · GHSA-f8mr-jv2c-v8mg

Invalid root may become trusted root in The Update Framework (TUF)

CVSS 8.7 HighEPSS 0.0067 · 52nd percentile

Published by the GitHub Advisory Database at 9 Sept 2020, 17:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
tufPyPI<0.12.00.12.0
Identifiers
GHSA-f8mr-jv2c-v8mg · CVE-2020-15163 · PYSEC-2020-145
Weakness (CWE)
CWE-345 · CWE-863
Published
9 Sept 2020
Updated
10 Sept 2026

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.

Written 5 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:38 UTC First seen by agentprime
  2. 31 Oct 2026, 14:38 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.