CVE-2026-24686: fallo de gravedad media en theupdateframework go-tuf
go-tuf Path Traversal in TAP 4 Multirepo Client Allows Arbitrary File Write via Malicious Repository Names
Publicada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 4.7epss 0.2%
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.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
Productos afectados
theupdateframework · go-tufCVEs relacionadas — theupdateframework go-tuf
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-23991MEDIUMgo-tuf affected by client DoS via malformed server responseEPSS 0.6%CVE-2022-29173HIGHNo protection against rollback attacks in go-tufEPSS 0.6%CVE-2024-47534HIGHIncorrect delegation lookups can make go-tuf download the wrong artifactEPSS 0.5%CVE-2026-23992MEDIUMgo-tuf improperly validates the configured threshold for delegationsEPSS 0.2%