What’s Vulnerable › Vulnerabilities

CVE-2026-24686: go-tuf Path Traversal in TAP 4 Multirepo Client Allows Arbitrary File Write via Malicious Repository Names

• Severity: medium (CVSS 4.7 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-01-27 · updated 2026-06-17
• Weakness: CWE-22

Description

go-tuf is a Go implementation of The Update Framework (TUF). go-tuf's TAP 4 Multirepo Client uses the map file repository name string (`repoName`) as a filesystem path component when selecting the local metadata cache directory. Starting in version 2.0.0 and prior to version 2.4.1, if an application accepts a map file from an untrusted source, an attacker can supply a `repoName` containing traversal (e.g., `../escaped-repo`) and cause go-tuf to create directories and write the root metadata file outside the intended `LocalMetadataDir` cache base, within the running process's filesystem permissions. Version 2.4.1 contains a patch.

Affected products

• theupdateframework go-tuf: from 2.0.0 before 2.4.1 — fixed in 2.4.1

How to fix

Upgrade to a fixed version: theupdateframework go-tuf 2.4.1. Check the vendor advisory for mitigations.

References

• https://github.com/theupdateframework/go-tuf/commit/d361e2ea24e427581343dee5c7a32b485d79fcc0
• https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-jqc5-w2xx-5vq4

Get alerted when CVE-2026-24686 or the next vulnerability affects your stack