Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 3.1 4.7 MEDIUMEUVD CVSS 3.1 4.7 CVSS 3.1 · [email protected] · Secondary 4.7 MEDIUMCVSS 3.1 · [email protected] · Primary 4.7 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/theupdateframework/go-tuf/v2 2.4.1osv · severity unknownFixed by github.com/theupdateframework/go-tuf/v2 2.4.1KEV status unknown

cve-program · CVE-2026-24686

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-4837

Published

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.

Read the publisher's advisory

nvd · CVE-2026-24686

Published

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.

Read the publisher's advisory

osv · GHSA-jqc5-w2xx-5vq4

Published

# Security Vulnerability: Path Traversal in TAP 4 Multirepo Client ## Summary 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. 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. ## Affected Component | Field | Value | |-------|-------| | **File** | `metadata/multirepo/multirepo.go` | | **Function** | `(*MultiRepoClient) initTUFClients() error` | | **Callsite** | `metadataDir := filepath.Join(client.Config.LocalMetadataDir, repoName)` (around line 129 at the pinned commit) | ## Impact When the TAP 4 map file content is attacker-controlled, this enables arbitrary file write relative to the process permissions (via metadata persistence during client initialization). This can be used to overwrite files writable by the process (for example, configuration files in writable directories) and may enable further compromise depending on the deployment environment. > **Note:** Exploitability is deployment-dependent. If the map file is always local and trusted (not attacker-controlled), this reduces to a misconfiguration risk rather than a remotely triggerable issue. ## Attacker Model - Attacker can cause the application to load a TAP 4 map file whose `repositories` keys are attacker-controlled (for example: fetched from a URL, supply-chain substituted, or otherwise attacker-influenced input). - Local caching is enabled (`DisableLocalCache=false`) and the configured `LocalMetadataDir` is writable by the running process. **Claim Ceiling:** HIGH when the map file is attacker-controlled; if the map file is always local and trusted, this is closer to a configuration footgun and likely lands as MEDIUM/LOW. | Field | Value | |-------|-------| | **Affected Versions** | ≤ 2.4.0 | | **Verified On** | Commit `bde5f18dc95dfac365fc452ee4e278e5fd66d4b4` (tag v2.4.0) | > **Note:** First affected version has not been bisected. ## Reproduction Attachments include `poc.zip` with: - `canonical.log` (contains `[CALLSITE_HIT]`, `[PROOF_MARKER]`) - `control.log` (contains `[CALLSITE_HIT]`, `[NC_MARKER]`, does not contain `[PROOF_MARKER]`) - `fix.patch` (minimal validation sketch) **Expected:** Multirepo repository names are treated as identifiers; a TAP 4 map file containing traversal or absolute paths is rejected (or safely normalized so that all writes stay under `LocalMetadataDir`). **Actual:** A traversal `repoName` escapes `LocalMetadataDir` and go-tuf persists `root.json` under the escaped path during initialization. ### Run Local Repro ```bash rm -rf _poc mkdir -p _poc unzip -q -o poc.zip -d _poc cd _poc/poc make canonical make control ``` ## Workarounds 1. Treat TAP 4 map files as trusted configuration only (do not fetch from untrusted sources). 2. Validate repo names before passing the map file to go-tuf (reject absolute paths, path separators, and traversal components like `.` / `..`). 3. If acceptable for the application, disable local caching to avoid writing metadata to disk (`DisableLocalCache=true`). ## Suggested Remediation Validate multirepo repository names as identifiers (not paths) before using them in `filepath.Join`. Reject: - Absolute paths - Path separators (`/` and `\`) - Traversal components (`.` and `..`) If it is important to accept a wider set of repo names, a safer alternative is to map repo names to a stable, validated directory name (for example via encoding or hashing) and to ensure all writes stay under the cache base directory. ## Triage Questions 1. Is the TAP 4 map file expected to ever be fetched from untrusted sources in supported deployments? 2. Should invalid repo names be treated as a hard error (reject initialization), or as a soft error (skip that repository entry)? ## Attachments - [poc.zip](https://github.com/user-attachments/files/24849854/poc.zip) - [addendum.md](https://github.com/user-attachments/files/24849855/addendum.md) - [e2e.zip](https://github.com/user-attachments/files/24849856/e2e.zip) - [PR_DESCRIPTION.md](https://github.com/user-attachments/files/24849858/PR_DESCRIPTION.md) --- *Reported by: Oleh*

Read the publisher's advisory

osv · GO-2026-4377

Published

Path traversal in TAP 4 multirepo client allows arbitrary file write via repo names in github.com/theupdateframework/go-tuf

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

14 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

15 Nov 2026 07:38:24 UTC

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…

euvd · EUVD-2026-4837 · Published

13 Nov 2026 07:03:19 UTC

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…

euvd · EUVD-2026-4837 · Published

11 Nov 2026 06:32:58 UTC

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…

euvd · EUVD-2026-4837 · Published

9 Nov 2026 06:08:28 UTC

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…

euvd · EUVD-2026-4837 · Published

7 Nov 2026 05:32:10 UTC

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…

euvd · EUVD-2026-4837 · Published

5 Nov 2026 05:01:22 UTC

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…

euvd · EUVD-2026-4837 · Published

3 Nov 2026 04:05:09 UTC

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…

euvd · EUVD-2026-4837 · Published

1 Nov 2026 03:11:34 UTC

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…

euvd · EUVD-2026-4837 · Published

30 Oct 2026 02:55:53 UTC

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…

euvd · EUVD-2026-4837 · Published

28 Oct 2026 02:07:06 UTC

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…

euvd · EUVD-2026-4837 · Published

25 Oct 2026 06:17:10 UTC

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…

nvd · CVE-2026-24686 · Published

24 Oct 2026 13:19:41 UTC

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

osv · GHSA-jqc5-w2xx-5vq4 · Published

24 Oct 2026 13:19:41 UTC

Path traversal in TAP 4 multirepo client allows arbitrary file write via repo names in github.com/theupdateframework/go-tuf

osv · GO-2026-4377 · Published

23 Oct 2026 15:48:27 UTC

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

cve-program · CVE-2026-24686 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current