Metrics
Affected Vendors & Products
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-jqc5-w2xx-5vq4 | go-tuf Path Traversal in TAP 4 Multirepo Client Allows Arbitrary File Write via Malicious Repository Names |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 27 Jan 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 27 Jan 2026 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Theupdateframework
Theupdateframework go-tuf |
|
| Vendors & Products |
Theupdateframework
Theupdateframework go-tuf |
Tue, 27 Jan 2026 01:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | go-tuf Path Traversal in TAP 4 Multirepo Client Allows Arbitrary File Write via Malicious Repository Names | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-27T14:40:01.511Z
Reserved: 2026-01-23T20:40:23.389Z
Link: CVE-2026-24686
Updated: 2026-01-27T14:39:48.632Z
Status : Awaiting Analysis
Published: 2026-01-27T01:16:02.790
Modified: 2026-01-27T14:59:34.073
Link: CVE-2026-24686
No data.
OpenCVE Enrichment
Updated: 2026-01-27T09:02:59Z
Github GHSA