Client metadata path-traversal
Impact
In both clients (tuf/client and tuf/ngclient), there is a path traversal vulnerability that in the worst case can overwrite files ending in .json anywhere on the client system on a call to get_one_valid_targetinfo(). It occurs because the rolename is used to form the filename, and may contain path traversal characters (ie ../../name.json).
The impact is mitigated by a few facts:
- It only affects implementations that allow arbitrary rolename selection for delegated targets metadata
- The attack requires the ability to A) insert new metadata for the path-traversing role and B) get the role delegated by an existing targets metadata
- The written file content is heavily restricted since it needs to be a valid, signed targets file. The file extension is always .json.
Patches
A fix is available in version 0.19 or newer.
Workarounds
None that do not require code changes. Clients can restrict the allowed character set for rolenames, or they can store metadata in files named in a way that is not vulnerable: neither of these approaches is possible without modifying python-tuf.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in python-tuf
- Contact the maintainers by email or Slack
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | tuf | < 0.19.0 | 0.19.0 |
References
- https://github.com/theupdateframework/python-tuf/commit/4ad7ae48fda594b640139c3b7eae21ed5155a102
- https://github.com/theupdateframework/python-tuf/security/advisories/GHSA-wjw6-2cqr-j4qr
- https://github.com/theupdateframework/python-tuf/issues/1527
- https://nvd.nist.gov/vuln/detail/CVE-2021-41131
- https://github.com/pypa/advisory-database/tree/main/vulns/tuf/PYSEC-2021-376.yaml
- https://github.com/theupdateframework/python-tuf
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N- Weakness (CWE)
CWE-22- Platform
- Python (PyPI)
- Package
tuf- Disclosed
- 19.10.2021
- Updated
- 11.10.2026 13:19
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2021-376 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-wjw6-2cqr-j4qr - CC BY 4.0
Vulnerability history: tuf
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 7
- First → latest
- 01.2020 05.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 1
- Medium 4
- Low 2
Disclosures per year
- 2020: 3
- 2021: 1
- 2022: 1
- 2023: 0
- 2024: 1
- 2025: 0
- 2026: 1
-
Client metadata path-traversal this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.