CVE-2026-24686

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data tampering.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-01-27 01:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 10:23 UTC Last updatedMost recent change to the record

Details

Published

2026-01-27 01:16 UTC

Last modified

2026-06-17 10:23 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-22 · Path traversal

Record status

Analyzed

Affected

• Theupdateframework go-tuf < 2.4.1

Attack profile CVSS 3.1 · 4.7

Attack vector

Local

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None