Arbitrary file write via repository-name path traversal
Published Jan 27, 2026 · Updated Jan 27, 2026
Path traversal in go-tuf 2.0.0 through 2.4.0 allows attackers to write root metadata outside the local cache directory. MultiRepoClient.initTUFClients joins an unvalidated repoName from a TAP 4 map file to LocalMetadataDir, allowing traversal components to escape the cache base. Exploitation requires attacker-controlled map data, enabled local caching, and a cache path writable by the process; resulting writes remain limited by that process's filesystem permissions.
Summary
What happened
Path traversal in go-tuf 2.0.0 through 2.4.0 allows attackers to write root metadata outside the local cache directory. MultiRepoClient.initTUFClients joins an unvalidated repoName from a TAP 4 map file to LocalMetadataDir, allowing traversal components to escape the cache base. Exploitation requires attacker-controlled map data, enabled local caching, and a cache path writable by the process; resulting writes remain limited by that process's filesystem permissions.
The record
- CVE
- CVE-2026-24686
- Published
- Jan 27, 2026
- Updated
- Jan 27, 2026
- Vendor
- The Update Framework
- Product
- go-tuf
- Classifications
- CWE-22, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 27, 2026CVE publishedPublication date reported by the CVE source.
- Jan 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.0.0, < 2.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream TAP 4 path-traversal reproduction bundleproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo