# CVE-2026-24686: go-tuf Path Traversal in TAP 4 Multirepo Client Allows Arbitrary File Write via Malicious Repository Names > An attacker can write arbitrary files outside the intended cache directory by supplying malicious repository names in the go-tuf TAP 4 Multirepo Client. - **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Jan 2026 - **Updated:** 27 Jan 2026 - **Also known as:** BELL-CVE-2026-24686, CLEANSTART-2026-AP98474, CLEANSTART-2026-BV58345, DEBIAN-CVE-2026-24686, GHSA-jqc5-w2xx-5vq4, GO-2026-4377, MINI-2f3g-pmh6-5w9v, MINI-338m-4wh4-9pqm, MINI-3cc8-33jx-9m8r, MINI-3f9v-6w4m-4wmf, MINI-4j42-f456-vp2v, MINI-6c4m-q3vf-4f7p, MINI-6crw-ph6f-c7q6, MINI-7wf4-75v6-fj6g, MINI-8f95-9wr5-8f3p, MINI-8g9r-52pq-h265, MINI-8m8g-jg9p-86vj, MINI-9wmg-85cq-pv62, MINI-fjgf-mhj6-j5jq, MINI-g452-qvpc-37m5, MINI-g64w-8g99-c6w9, MINI-h9pp-mchm-wx5j, MINI-hpq2-rqr8-pq6m, MINI-hpxc-m83x-r653, MINI-m9xm-582m-2wwh, MINI-mf6q-vr8m-rrjx, MINI-pfhw-h3mw-q539, MINI-qjvq-6q5c-cg83, MINI-qmph-3758-7r2f, MINI-rhw9-32cm-gqrh, MINI-v32j-7mh9-56c5, MINI-vvhf-cg3p-5cvq, MINI-w3hf-c9cw-223v, MINI-w9gh-pxcg-2f9c, MINI-wf64-wjj8-j5g2, MINI-wjpg-77w8-267c, MINI-wmfm-x9h2-v24x, MINI-xfw9-9w56-mfwx, MINI-xwh5-mgv6-4r86, UBUNTU-CVE-2026-24686 ## What is CVE-2026-24686? CVE-2026-24686 is a medium-severity path traversal vulnerability in theupdateframework go-tuf, published on 27 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-24686? 3 open source packages ship an affected version, including github.com/theupdateframework/go-tuf/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/theupdateframework/go-tuf/v2` | Go | All versions | 2.4.1 | | `github.com/theupdateframework/go-tuf/v2` | Go | All versions | 2.4.1 | | `github.com/theupdateframework/go-tuf/v2` | Go | All versions | 2.4.1 | Products: Theupdateframework Go-Tuf. ## How do I fix CVE-2026-24686? Upgrade github.com/theupdateframework/go-tuf/v2 to 2.4.1 or later. ## Is CVE-2026-24686 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24686 exists. ## Other vulnerabilities in theupdateframework go-tuf - [CVE-2022-29173](https://insights.sbomify.com/CVE-2022-29173/): No protection against rollback attacks in go-tuf (high 8.0) - [CVE-2026-23991](https://insights.sbomify.com/CVE-2026-23991/): go-tuf affected by client DoS via malformed server response (medium 5.9) - [CVE-2026-23992](https://insights.sbomify.com/CVE-2026-23992/): go-tuf improperly validates the configured threshold for delegations (medium 5.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-24686 and fix it if it is affected. What it is: CVE-2026-24686 is a medium-severity path traversal vulnerability in theupdateframework go-tuf, published on 27 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24686 exists. Affected packages and fixed versions: - github.com/theupdateframework/go-tuf/v2 (Go): affected all versions; fixed in 2.4.1 - github.com/theupdateframework/go-tuf/v2 (Go): affected all versions; fixed in 2.4.1 - github.com/theupdateframework/go-tuf/v2 (Go): affected all versions; fixed in 2.4.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-24686/ (Markdown: https://insights.sbomify.com/CVE-2026-24686/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24686 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24686 - OSV: https://osv.dev/vulnerability/CVE-2026-24686 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-24686/ Summaries are generated and may contain mistakes; the official description above is the record.