Security readout for executives and security teams
Plain-English summary
CVE-2026-24686 affects go-tuf applications using the TAP 4 Multirepo Client. If they accept a map file from an untrusted source, a malicious repository name can make the application write metadata outside its intended cache directory. The issue is patched in go-tuf 2.4.1.
Executive priority
Treat as a targeted dependency remediation item, not an emergency. Prioritize systems that process externally supplied update metadata or run with broad write access.
Technical view
go-tuf versions 2.0.0 through before 2.4.1 use the map file repoName as a filesystem path component for the local metadata cache. Traversal sequences can escape LocalMetadataDir and cause root metadata file writes within the process permissions. This is CWE-22 path traversal with CVSS 4.7.
Likely exposure
Exposure is limited to applications using affected go-tuf versions and the TAP 4 Multirepo Client, especially where map files may be attacker-controlled or supplied by untrusted sources.
Exploitation context
No active exploitation is indicated in the provided sources, and KEV is false. Exploitation depends on getting an application to process a malicious map file and is constrained by the process filesystem permissions.
Researcher notes
The advisory’s key condition is untrusted map file input. Analysis should focus on call paths into TAP 4 Multirepo Client behavior, repoName handling, LocalMetadataDir boundaries, and the deployed process privilege model.
Mitigation direction
- Upgrade go-tuf to version 2.4.1 or later.
- Avoid accepting TAP 4 map files from untrusted sources.
- Run affected applications with minimal filesystem write permissions.
- Review vendor advisory and commit details for implementation-specific guidance.
Validation and detection
- Inventory applications and dependencies using go-tuf.
- Identify versions from 2.0.0 through before 2.4.1.
- Confirm whether the TAP 4 Multirepo Client is used.
- Check whether map files can originate from untrusted sources.
- Verify deployed builds use go-tuf 2.4.1 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24686 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N13.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.7MediumVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-jqc5-w2xx-5vq4CVE reference · x_refsource_CONFIRM
- https://github.com/theupdateframework/go-tuf/commit/d361e2ea24e427581343dee5c7a32b485d79fcc0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.